Computer-guided corporate governance with document generation and execution

ABSTRACT

A system for corporate governance and for organizing, managing, and reporting data relating to a corporate entity is described. A database is configured to store a core record with a document record. A business logic module, coupled to the database, uses instructions in a document template for generating a document based on the core record, the core record further comprising a value reflecting human-readable information to be incorporated into the generated document, the core record further comprising a provenance of the value for allowing the business logic module to assess validity of the value at a given time by evaluating where the value was originated, the business logic module thereby enabling the system to verifiably generate documents that reflect a present state of the corporate entity.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority under 35 U.S.C. §119(e)of U.S. Pat. App. No. 61/935,548, entitled “Computer-guided CorporateGovernance through use of Core-Record-driven Document Generation andProcess Automation” and filed Feb. 4, 2014, and U.S. Pat. App. No.62/024,434, entitled “Computer-guided Corporate Governance through useof Core-Record-driven Document Generation and Process Automation” andfiled Jul. 14, 2014, both of which are hereby incorporated by referencein their entirety for all purposes.

BACKGROUND

One of the major obstacles for entrepreneurs founding a startup isnavigating the legal landscape of corporate governance. From the momentof incorporation, founders must prepare and execute legal documentsrelated to company formation. The preparation, tracking, and complianceobligations continue through all stages of building a startup, andrequire preparation of documents such as non-disclosure agreements,consulting and employment agreements, equity management agreements,documents for financing, documents for auditing, mergers andacquisitions documents, minutes for board meetings, etc. Few optionsexist for mitigating the complexity of creating these documents, andexisting solutions that attempt to provide template documents aretransaction-centric, disconnected from one another, and do little toeducate the founders about the legal implications and ongoingobligations owed by the company. As a result, representations are oftenneglected, board minutes are compiled once a year from notes, andimportant documents are back-dated to align timelines. In the end, whenthe company seeks additional funding or is considered for acquisition,it is often stuck with a literal or figurative shoebox ofhaphazardly-collected legal documents, and it is the company that paysfor the correction of any legal irregularities that result.

While the plain document management aspect of the problem can be solvedby using content management system (CMS) or data room software, allexisting solutions today just scratch the surface of the problem. Whotracks that the documents are consistent with each other? Are we surethat legal professionals do not miss inconsistencies while reviewinghundreds of employment contracts? How do we even know whether a documentis relevant? Who tells the founders when certain action is needed? Whoenforces the legal framework described in the documents? How can onedetermine and track the accuracy of information within a document? Whotracks the origin of information within a document? How do you know thatthe place from which a certain piece of information was copied was anaccurate source? Who oversees permissions and general process flow?

A fundamental, holistic approach is needed that changes the legallandscape of corporate governance. Such an approach is described herein,and can be thought of as a Business Operating System.

SUMMARY

In one embodiment, a system may be disclosed for organizing, managing,and reporting data relating to a corporate entity, comprising at leastone database configured to store a document record and a core record,the document record relating to a corporate action, the core recordstored with the document record; a business logic module, coupled to theat least one database; and at least one document template stored in theat least one database and comprising instructions for generating, at thebusiness logic module, a document based on the core record, the corerecord further comprising a value reflecting human-readable informationto be incorporated into the generated document, the core record furthercomprising a provenance of the value for allowing the business logicmodule to assess validity of the value at a given time by evaluatingwhere the value was originated, the business logic module therebyenabling the system to verifiably generate documents that reflect apresent state of the corporate entity.

The provenance may be a source document object or an indication that thevalue was manually entered by a stakeholder. A user interface may becoupled to the business logic module for displaying the generateddocument to a user for signature. The at least one database may beconfigured to store an entity object, the entity object furthercomprising a set of entity records with each entity record of the set ofentity records comprising a value and a provenance of the value, whereinat least one entity record of the set of entity records includes aprovenance that may be the document object relating to the corporateaction. A plurality of processors may be coupled to a database over anetwork. An authentication module and an electronic signature managermay be configured to insert signatures into generated documents. Aretrieval module may be configured to accept a signature uniqueidentifier or quick response (QR) code related to a signature on apreviously-executed document for retrieving the stored document. Adelegation manager may be configured to perform authorization to performan action in the system using one or more of permissions, roles,principals or groups, and configured to permit principals to delegate apermission or role to another principal in the context of a particularentity, document, or process. The user interface may be coupled to thebusiness logic module, wherein the user interface may be configured todisplay available stakeholder capabilities, the stakeholder capabilitiesenabling a user to modify an entity record through a process. Thegenerated document may be a portable document format (PDF) document. Thebusiness logic module may be configured to retrieve, for a given entityrecord, a prior-generated document storing a core record referenced bythe given entity record and with an active status stored in a tag of theprior-generated document.

In another embodiment, a method may be disclosed for organizing,managing, and reporting data relating to a corporate entity, comprising:retrieving an entity record comprising a value and a lineage entry, thelineage entry comprising a value source, the value source referencing afirst document; retrieving a corporate action stored as acomputer-readable process definition; creating a core record for asecond document based on at least one of the entity record, astakeholder record, or manual input; and generating the second documentusing the core record and a document template.

The method may include retrieving a permissibility rule associated witha corporate action and an active stakeholder role; and determining,based on the permissibility rule and the stakeholder role, whether astakeholder may be authorized to perform the corporate action. Themethod may include storing an active document status with the seconddocument; and retrieving a set of documents that includes the seconddocument in response to a query for all active documents, therebyenabling a user to retrieve documents that reflect a present state ofthe entity. The method may include retrieving an updated value from anew core record within the second document; updating the entity recordwith the updated value; and adding, to the entity record, a new lineageentry with a value source referencing the second document, therebypreserving the first document without modification. The first documentmay be a certificate of incorporation, and the first core record may bea corporation name referenced in the certificate of incorporation. Thesecond document may be one of a board resolution, a shareholder consent,a shareholder communication, and a stock plan. Alternatively, the firstdocument may be a certificate of incorporation, and the second documentmay be an amendment to the certificate of incorporation.

In another embodiment, a system may be disclosed, comprising a processorfor performing data storage and retrieval operations; a database coupledto the processor; and a storage medium comprising instructions which,when executed by the processor, performs steps comprising: retrieving anentity record comprising a value and a lineage entry, the lineage entrycomprising a value source, the value source referencing a firstdocument; retrieving a corporate action stored as a computer-readableprocess definition; creating a core record for a second document basedon at least one of the entity record, a stakeholder record, or manualinput; and generating the second document using the core record and adocument template.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of high-level components of an overallsystem, in accordance with some embodiments.

FIG. 2 is a schematic diagram of an application server, in accordancewith some embodiments.

FIG. 3 is a schematic diagram of a database server, in accordance withsome embodiments.

FIG. 4 is a schematic diagram of a data model, in accordance with someembodiments.

FIG. 5 is a schematic diagram of a document, in accordance with someembodiments.

FIG. 6 is a schematic diagram of a document template, in accordance withsome embodiments.

FIG. 7 is a schematic diagram of a core record, in accordance with someembodiments.

FIG. 8 is a schematic diagram of a workflow execution engine andcomponents relating thereto, in accordance with some embodiments.

FIG. 9 is a schematic diagram of a user interface in conjunction with aworkflow execution engine, in accordance with some embodiments.

FIG. 10 is a schematic diagram of an information structure, inaccordance with some embodiments.

FIG. 11 is a schematic diagram of a record schema, in accordance withsome embodiments.

FIG. 12 is a schematic diagram of a document templating architecture, inaccordance with some embodiments.

FIG. 13 is a schematic diagram of components of a signature, inaccordance with some embodiments.

FIG. 14 is a schematic diagram of document lookup via signature QRcodes, in accordance with some embodiments.

FIG. 15 is a schematic diagram of users and stakeholders and theirsecurity roles, in accordance with some embodiments.

FIG. 16 is a schematic diagram of components involved in modifyingand/or amending a document, in accordance with some embodiments.

FIG. 17 is a flowchart of a process that generates a document, inaccordance with some embodiments.

FIG. 18 is a wireframe diagram of a terms selection page for aparticular section of a document featuring analytics-based decisionsupport, in accordance with some embodiments.

FIG. 19 is a schematic diagram of an example report card for anon-disclosure agreement, in accordance with some embodiments.

DETAILED DESCRIPTION

The distributed, cloud-based system described herein provides a set ofapplications to properly govern a corporation or other entity covered bythe system. At its core, the system maintains documents in arepresentation that retains core records in a computer-processable form,each defining business information about the corporation and also storedwith a lineage defining a value source for each core record. The systemapplies legal workflow processes to guide generation of documents fromcomputer-processable document templates, and captures approvals andsignatures as evidence of agreement by the parties. The data capturedmay also be used to guide compliance, drive decision support, andprovide reporting.

Some embodiments described herein are also capable of analyzing internaldocument consistency, identifying key documents, creating anchordocuments used as sources of information, and calculating thereliability of documents either individually or as part of an overallprocess in order to meet diligence or compliance objectives.

Examples of processes that may be facilitated by the use of variousembodiments as described herein include: forming a new company,including identifying board members, founders, and stock distributionsthereto; adopting corporate by-laws; creating meeting minutes for aboard meeting; creating shares authorized by the board of directors;creating board member and shareholder resolutions; creating board memberconsents; creating non-disclosure agreements; adding and/or removingemployees, consultants, board members, corporate officers, or otherpersons relating to the company; sending, and/or receiving notificationsrelating to creation of board member resolutions, and/or consentsthereto; granting and/or exercising stock options; approving wiretransfers, e.g., for the exercise of stock options; creating debt notesor equity financing documents; and initiating investor capital calls,among other processes. In some embodiments, forming a new company mayinclude the creation of formation documents, formalizing the membershipof the initial board, identifying the specific legal structure ofincorporation, and the distribution and/or issuance of stock to foundersand/or board members.

DEFINITIONS

In some embodiments, as used herein, “amendment” may refer to anaddition of supplemental information to an executed document. Suchadditions are made at the granularity of a document section. Theavailability of an amendment for a document section is defined in thedocument template, so that that sections critical to the system are notchanged.

In some embodiments, as used herein, “analytic decision support” mayrefer to a mechanism to help a user select the best term within aparticular context. The analytics includes usage data, legal reviews, oruser ratings. The context considers many dimensions from historicalstakeholder data, entity data, geography and time.

In some embodiments, as used herein, “application” may refer to a set offunctionalities that represents a particular aspect of corporategovernance within the context of a role. Applications are comprised of asummary dashboard panel and a set of pages fulfilling the functionalityof the aspect.

In some embodiments, as used herein, “business operating system” mayrefer to the collective system used to execute corporate governance.

In some embodiments, as used herein, “capability” may refer to theability to perform an action based on permissions, roles, and groups.

In some embodiments, as used herein, “confidence indicator” may refer toan aggregate metric that represents a measure of the data quality,history and trust of a document. Contributing quality metrics include:Origin (template/upload), e-signature status, and core records origin.The computed value can be displayed to the user in a quantitative orqualitative manner.

In some embodiments, as used herein, “core record” may refer tocomputer-processable, structured data that represents the coreinformation contained within a document along with the lineage entry.Core records are grouped in sets that reflect various aspects of thedata. For system-rendered documents, the core records are used inconjunction with a document template to generate a printable document.In some embodiments, core records are a fundamental record in adocument, from which stakeholder records and entity records are derived.

In some embodiments, as used herein, “core record field” may refer to asingle field within the core record schema. Types of core record fieldsinclude number, text, list, lookup maps, record, date/time, money,signature, and document and stakeholder reference.

In some embodiments, as used herein, “core record schema” may refer to aset of core record fields that describe one subject area of the corerecords. Core record schemas can be either defined specifically for onedocument template or for a group of document templates where astandardized data set is needed to effectively analyze the data.

In some embodiments, as used herein, “corporate action” may refer to aset of steps, usually encapsulated in a process, that execute a specifictask within corporate governance. Corporate actions are accessible tothe user via links in the corporate actions menu that serve as entrypoints.

In some embodiments, as used herein, “corporate governance” may refer tothe system of rules, practices and business processes by which a companyis directed and controlled, how it discloses and interacts withstakeholders, and/or how it is audited and evaluated in the course oflegal diligence. Corporate governance essentially involves balancing theinterests of the many stakeholders in a corporate entity. These mayinclude, but are not limited to, its shareholders, employees,management, customers, suppliers, financiers, government and thecommunity as a whole.

In some embodiments, as used herein, “Delaware corporate execution” mayrefer to the set of legal processes needed to govern a Delawarecorporation as required by Delaware corporate law.

In some embodiments, as used herein, “delegation set” may refer to a setof permissions and roles that that can be delegated to another user in aparticular context. The delegation set also contains a title,description and a set of roles required by a user to use the delegation.These sets can be freely defined via configuration.

In some embodiments, as used herein, “document” or “document object” mayrefer to the electronic form of a document, its core records, tags,report card, authenticity and certification. Physical copies can beprinted on demand. Documents can either be uploaded files or generatedfrom predefined document templates. In addition, documents are linked tosets of core records, which are information from the document contentsstored in a structured, computer-processable manner. Once a document hasbeen executed it is immutable by leveraging cryptographic signatures toprotect against unauthorized changes.

In some embodiments, as used herein, “document modification” may referto a replacement of a document section with manually-crafted subjectmatter content. The availability of a modification for a documentsection is defined in the document template.

In some embodiments, as used herein, “document section” may refer to apart of a document that is used for organizational purposes. They aredefined in document templates and commonly have a header, body text andhelp text. Document sections are further used in the user interface tobreak up the document for the user.

In some embodiments, as used herein, “document template” may refer to anelectronic, computer-processable file that describes how to generate aprintable document such as a portable document format (PDF) file given aset of core records. The three components of a document template arerendering instructions, core records definitions, and business logic.

In some embodiments, as used herein, “document term” may refer to a keyelement in a document with a predefined set of options for a user tochoose from. The selected option will affect the content in thedocument, which can range from simple words/values to severalparagraphs. The selected option is captured as part of the document'score record.

In some embodiments, as used herein, “entity” may refer to acorporation, cooperative, partnership, or other legal organization withwhich it is possible to conduct business. The described system acts onbehalf of the entity and by doing so provides corporate governance forthe entity. Entities may be legal organizations.

In some embodiments, as used herein, “entity record” may refer tocomputer-processable, structured data that represents the coreinformation defining an entity. Entity records are grouped in sets thatreflect various aspects of the data, and include a value and lineageentries reflecting the full history of the particular entity record. Anentity record value is usually a copy of a core record value. An entityrecord includes, but is not limited to, values relating to one or moreof the membership of the board of directors, board of directors votingthresholds, classes of stock, conversion ratios to common stock, and howshareholder votes can be executed.

In some embodiments, as used herein, “external authority” may refer to atrusted third party that can provide certification, review or audit ofdocuments.

In some embodiments, as used herein, “key data” may refer to a subset ofcore records that is essential to the document and for which no goodautomatically-applied default exists. Key data may be manually input bya stakeholder to successfully render a document and for this document tobe properly handled by the system.

In some embodiments, as used herein, “lineage” may refer to metadata onentity records and stakeholder records that includes a historicalaccount of its values and its value source.

In some embodiments, as used herein, “lineage entry” may refer to asingle entry in the lineage that contains the old value, new value,timestamp and value source.

In some embodiments, as used herein, “market of terms” may refer to theconcept that user decisions on a choice of term will rise and fall inpopularity based on usage, legal review, negotiating leverage and thechoice's performance through legal challenges.

In some embodiments, as used herein, “permission” may refer to asecurity object representing the ability to complete a particularaction. It represents the finest grain of access control in the system.

In some embodiments, as used herein, “principal” may refer to a securityobject also commonly known as “subject” that represents a stakeholder inthe context of access control and security in general.

In some embodiments, as used herein, “process” may refer to a workflowthat is executed to achieve a corporate action or more generally anysystem objective. A process contains business logic and user interfaceinstructions that enable corporate actions to be completed. Userinterfaces are generated in a fully automated manner through the system.

In some embodiments, as used herein, “process definition” may refer to aset of data structures describing the execution paths of a process.Process definitions include activities, transitions, andcomputer-processable business logic.

In some embodiments, as used herein, “process execution engine” mayrefer to a module and/or executable code that reads process instructionsand executes them. Through the proper execution of the process, theengine enforces the correctness of the legal corporate governanceprocesses.

In some embodiments, as used herein, “report card” may refer to asummary of a document's quality including the confidence indicator,activity log, selected document terms, core records, and value source.

In some embodiments, as used herein, “role” may refer to refers to anabstract group of obligations and rights within an entity and can bedefined in documents or are commonly agreed upon. The system can assignroles to users via processes, administrative user interfaces, or throughdelegation by other users. Roles are security objects that represent aset of permissions. Examples of roles include associate (e.g., a thirdparty to a given entity), employee, manager (of one or more employees),corporate officer, board member, and administrator. A user may havemultiple roles. Each role may cause a corresponding dashboard in theuser interface to be exposed, and may define actions the user isauthorized to take on behalf of themselves or the company.

In some embodiments, as used herein, “section” may refer to a part of adocument that discusses a specific topic of the document matter. Itincludes content in the form of text, drawings and other printablematter; the terms; and the business logic to modify contents based onthe terms and other core records.

In some embodiments, as used herein, “secure data provenance” may referto metadata on entity records and core records defining the quality andorigin of data values that are stored with the document in a immutableway after document execution. Quality refers to the method in which datahas been gathered, who is responsible for the source of the data,ideally including information on the originator of the data. Securedprovenance refers to providing integrity and confidentiality guaranteesto provenance information that this metadata cannot be rewritten, andusers can specify who else can look into their actions on the object.

In some embodiments, as used herein, “signature” may refer to an imagecontaining either a screen-entered, uploaded or generated form of theuser's signature, or a representation thereof. In some embodiments, asignature on a document is given a unique id and encoded in a QuickResponse (QR) code encoding an URL, which can be used to find thecorresponding document at any time. Signatures are stored as part of thecore records of a document. The ESIGN act and analogous internationalagreements/laws can govern the legal definition of a signature.

In some embodiments, as used herein, “stakeholder” may refer to a singleindividual that is associated with an entity. Governance-centric rolesare used for authorization to provide access to corporate actions,processes, documents and applications.

In some embodiments, as used herein, “stakeholder record” may refer tocomputer-processable, structured data that represents the coreinformation defining a stakeholder. Stakeholder records are grouped insets that reflect various aspects of the data. Stakeholder records maybe entered by the stakeholder through the graphical user interface.

In some embodiments, as used herein, “standardization” may refer to aquality of a document referring to the degree of attention to bereceived by a document, as during an audit. If a document is standard itmay have common term values for the entity, the system has highconfidence in its content and its execution.

In some embodiments, as used herein, “tag” may refer to a keyworddescription of a document, effectively making it a flag, that may bestored and presented for editing as human-readable text. Tags arehierarchically organized through namespaces and can be matched at anylevel of the hierarchy. In addition, tags serve additional roles such asacting permissions, causing varied business logic behavior, andproviding custom user interface views.

In some embodiments, as used herein, “term” may refer to a field in thecore records that provides a choice of values for a high-level conceptwithin the subject matter. Specific options of the term can requirefurther data fields of the core records schema.

In some embodiments, as used herein, “user” may refer to an individualwithin the business operating system. A user has records that providedata about the individual in the system, which may include accesscredentials to the system. The credentials are used for authenticationof the user with the system.

In some embodiments, as used herein, “value source” may refer to themethod description of how and where a value was sourced. A value couldbe sourced from another system document's core records, stakeholderrecords, manual input by a stakeholder, or textual description. A valuesource may be a reference to another document, a reference to astakeholder's data, or an indication that the stakeholder entered itmanually.

System Overview

The functionality of the system described herein is facilitated in partby integration between information storage capabilities, processexecution, document generation and electronic signatures. The system mayinclude one or more computer devices that run one or more instances ofthe system. The graphical user interface is used to communicate withusers and external authorities. Via back-end Internet-enabled networkconnections, the system communicates with external document storagesystems to upload or download documents.

One objective of the system is to properly execute and enforce entitycorporate governance processes as defined by federal and state law. Thisis accomplished by executing corporate governance tasks via a set ofprocesses defined by computer-readable process definitions that areexecuted in a process execution engine. Features that are not directlytied to a process are implemented using programmed and configuredbusiness logic.

The core responsibilities of corporate governance processes are propercreation and execution of documents, management of entity record state,and administration of stakeholders and their roles within the entity.Documents are uploaded or generated from document templates. Documenttemplates may include core record definitions, document renderinginstructions, business logic, and a set of default tags. The corerecords definitions declares the core record schemas and data recordfields of the core record data used within the rendered document. Therendering instructions may include the rendering markup,document/rendering structure, and core record references. Thesecomponents are used to render the document into common publicationformats, for example PDF and HTML, where the core record references areused to insert the core record data into the document content. Thedocument/rendering structure can be used to extract pieces of thedocument, such as sections.

Corporate governance-related data is stored in entity records, whichtrack the current value and a chronologically-ordered list of lineageentries that may include one or more of the old value, new value,timestamp, and value source. Entity record schemas are used to definethe data to be stored. The system manages users outside the context ofthe entity. Stakeholders are specific to an entity and store any oftheir data in stakeholder records, their structure defined bystakeholder record schemas. However, documents are the a priori sourcefor any data about the entity. Both uploaded and generated documents mayinclude core records, binary file data, a report card, and tags.

The security manager component may restrict stakeholder access asdefined by the entity records, administrator setup and role delegation.

The system communicates via a network with external document storagesolutions to synchronize document binary file data. In some embodiments,examples of storage systems that could be used for document binary filedata include Box.com, Dropbox, Google Drive, a private WebDAV filestore, or any other cloud-based content storage solution.

E-Signatures

in order to truly reduce paper for documentation, it should be possibleto sign documents electronically. Since the passage of the ESIGN act in2000, electronic signatures have the same legal effects as traditionalsignatures. Under the law, the signature can be any text, including in aparticular font or an image. The signing occurs at the moment the signeeassigns the signature to a document by expressively clicking the “sign”button.

In some embodiments, a stakeholder may set up an electronic signature.Both the full signature and initials may be allowed. Setup may includeuploading an image of the stakeholder's physical signature, or thecreation of signature text and initial text together with the particulartext in which to display the signature.

A signature or list of signatures may be a special type of core recordfield. A signature core record field may include a timestamp, securitycode, stakeholder and document reference. A security code is a uniqueidentifier of the signature as applied by a stakeholder to this documentat the specified position, and may be a unique user identifier (UUID). Asignature is rendered within a signature block of a document, which mayinclude a pictorial representation inserted into the document. As asecurity measure, the security code of the signature is rendered as is aQR code and inserted as well. This allows anyone to scan the QR code andretrieve information about the document, such as the title and allsignatories to verify the authenticity of the document and thesignatures.

In some embodiments, whenever a document is signed, an audit log entrymay be created capturing the document ID, date/time, user and IPaddress. In addition, a security code, such as a 16-byte global uniqueidentifier (GUID), is created and logged. The security code is placedinto the document below the signature. Security codes may be unique inthe system, so that any given security code maps to a specific signaturein a specific document. In some embodiments, the security code of asignature can be used to look up documents. The codes may be typed inmanually, or a QR code or bar code may be scanned using a camera on amobile device to enter the code. In some embodiments, the security codecan also be used to verify the authenticity of a document. This can beaccomplished by scanning all security codes for a given document andasking the system whether there exists a document where all these codesare present. In some embodiments, verification may also show the nameand date of each signee for verification. This mechanism protectsagainst altering the signature image/text, altering the security code ofa signature, or replacing a signature with another. In some embodiments,Adobe Certified Document Services (CDS) cryptographic algorithms may beused upon signing to cause documents to become immutable after adocument is signed and finalized.

The e-signature management component then applies and certifies thesignatures on the document.

Documents

Documents can be generated and executed by the system based on corerecords or uploaded from an external source. Embodiments may capture thestakeholder, timestamp, and set an upload flag, which are used todetermine that a document was uploaded from an external source. In theseembodiments, core record information can be gathered manually.

Once a document has been executed, it cannot be changed, in someembodiments. However, a document can be amended through a systemprocess. An amendment is a change to a section in the document. Similarto a modification, an amendment is free form text to replace an entiresection of the executed document. Once the amendment to the document isready, the system executes the amendment and generates a document forthe amendment that contains a core data reference to the originaldocument amended. This is done so that the original document is leftunchanged. The new amendment document is executed and made immutablewith a reference to the original document. Whenever a document isrendered for viewing by the system, the system can query whether anyamendments have been made to it.

When a document is created, the system tracks whether a selected termwas one of the following: a default option; a entity default option; anon-default option; or a custom text option. This information may laterbe used for reporting purposes.

After execution, the document is stored and available for viewingpursuant to the permissions on the document. The document is storedindefinitely and cannot be deleted by a user of the system. The documentmay be used to register the triggering of future events, for example,the end of a contract's term. Events may also be registered based on thedocument's core records, for example a warning for a non-competeprovision after the relationship with an entity terminates.

Tags may store various information about a document in a human-readabletext format. For example, the “active” tag could be applied to adocument once it becomes legally effective. As another example, the tag“certificate of incorporation” could be applied to a document to assigna certain document type. Once a tag is applied, it may be used to searchfor and retrieve one or more documents. For example, using these twotags in combination, the active certificate of incorporation documentcould be retrieved. Tags may be used to create a searchable hierarchy ofdocuments. For example, the tag “governance” may be applied to alldocuments pertaining to corporate governance functions. Additionally,the more specific tag “governance: formation” may be applied to alldocuments pertaining to corporate entity formation. The system willstore both “governance” and “governance: formation” when only the lattertag is assigned. This allows the system to quickly allow search andretrieval of all governance-related documents. As another example, thetag “equity grant” represents a generic term pertaining to stock grants,while more specific tags may be assigned to properly relect types ofstock grants, such as “equity grant: incentive stock option,” “equitygrant: non-qualified option,” and “equity grant: restricted stockaward.” Tags may be applied at the time a document is made, or at alater date, such as when a document becomes active or inactive. Tags maybe applied at the time a document is made, or at a later date, such aswhen a document becomes active or inactive.

Another type of structured data the system tracks are the selected termswithin a document. Terms are by nature choices of a few differentoptions. The system may provide a default option. In addition entitiescan provide their own default options for document terms. In anembodiment, the non-disclosure agreement contains a term defining theduration of the agreement having the options of one year, two years, andperpetual, with one year being the default option. However, a particularcompany might decide that two years is more appropriate for theirbusiness and change that default option within the context of thatentity.

Information Storage and Quality

Whether documents are stored either in paper form, scanned electronicdocuments or text-processor generated electronic files, these formatsmay not facilitate capture of information about the contents of thedocument or its historical background. By contrast, when documents aregenerated by the system, according to in some embodiments, documents canbe generated from standardized document templates and may facilitate thecapture of information. The system can, in some embodiments, discourageuploading scanned documents for this reason. When documents aregenerated using provided and computed data, the compilation of this datais stored along with the generated file as core records.

In addition, the system tracks the value source of the core recordsentries. For example, a document may reference the entity's legal nameby pulling the current value of the legal name from the appropriateentity record. In one embodiment, the current value of the entity'slegal name could have been obtained from an executed certificate ofincorporation document. This may mean the document's core record storingthe legal name for the document may include a value source referring tothe executed certificate of incorporation. Other examples of origins ofa value source could come from a stakeholder's manual input into thesystem or a stakeholder record.

Confidence Rating

Confidence of a document in the system is derived from the value sourceof its core records, source of document generation, and mode ofexecution. The inputs to whether a value source is trusted would includewhether the value source is from a document or simply manual user input.In the case of a document, the criteria of trust for the value source issimilar as how the document itself would be judged. Was the documentgenerated by the system or was it uploaded externally? Has the contentof the document been verified by an external authority? Was the documentexecuted within the system? How much trust does the system have with anysigners of the document? These measures help stakeholders and auditorsunderstand how much the system can verify about the document to informwhether one should trust the content of the document and its core recordmetadata. Manual entry of information or sources of information mayintroduce or increase the possibility of human error into the system, ifa user enters data that does not correctly reflect the informationencoded in the system about the document. This may affect the confidenceindicator, since there is no way to verify the core record datacollected in an upload scenario without third-party review.

Standardization

The level of standardization of a document in this system is derivedfrom source of document generation, use of modification or amendment,mode of execution, and choice of term values. Was the document generatedby the system? Was the content of the document text customized through afree-form text modification? Was the document executed within thesystem? Are the terms the stakeholder chose for the document standardfor the entity or custom? These factors play into whether certaindocuments merit additional attention during legal diligence.

To give the user a quick idea about the quality of a given document, thesystem provides a report card, which may include a confidence indicator,an action audit, a term summary, and a list of core records includingvalue source. The confidence indicator is computed from core records andmetadata of the document. The best score that a document can receive maybe set to one hundred, in some embodiments. In this embodiment, adocument having a score of one hundred would have the followingattributes: It was generated from a document template; its terms are alldefault terms; there are no document modifications; it was signed bystakeholders via the system; and it has a value source of highestconfidence. The score decreases, for example, if a document has beenuploaded and no e-signatures were applied. The confidence indicator,along with other document quality data, may be collected and attached asthe document report card. The aforementioned functionality can then beused to quickly validate the state of corporate documentation, which cangreatly reduce the volume of documents to be reviewed by outsideexperts, such as attorneys, auditors, or the like.

Processes

During execution of processes generating one or more documents, adocument template defines which core records need to be filled out tocomplete the document. The core records are seeded by computing as manydefault values as possible. The business logic defined in a processprovides the user with a guided workflow to capture core record datawhich can require user input. Other core record data can be capturedfrom entity records and previously executed document core records. Thedocument template also defines an initial set of tags that identify whattype of document will be generated, how it should be categorized, and aninitial status. Once enough information has been captured to generatethe document, a graphical user interface renders an interactive previewfor the stakeholder.

This interactive preview breaks the document into sections that aredefined by the document template of that document. Within each section,the document terms and core record fields that are specific to thesection are exposed and available for input as configured in thedocument template. At this stage, sections may also be available fordocument modification as defined within the document template, whichallows for changes to the document content at the granularity of asection. A document modification can negatively affect documentconfidence and could affect the ability of the system to automate futurecorporate governance processes. The stakeholder can then review andrelease the document for execution. The process's business logic definesthe execution process. Execution may include but is not limited to acollection of electronic signatures on the document or externalapproval, e.g. board or shareholder approval. The system signals that adocument is executed by changing its status tag.

In a user uploaded document-based process, the document is uploaded andbusiness logic defines what core record information should be collectedmanually from the user. Once the information has been captured, it canbe released for finalization.

Once a document has been executed through signature or approval, theprocess completes the document by cryptographically signing it to verifythat there have been no changes after finalization. This includes thedocument's binary file as well as the core records related to thedocument.

During the execution of a document, the process may define that thisdocument defines or changes an entry of an entity record. In such cases,the process will push a new value including a lineage entry into theentity record. The previous value is preserved in the lineage historybut going forward, any document referencing the updated field willreceive the value as defined by the new document. In one embodiment, theentity executes an amendment to the certificate of incorporation tochange the number of authorized shares of the entity. The process willdefine that the amendment the stakeholder performed with Delawaredefined the new value of “number of authorized shares” and will push thenew value and its value source (the amendment to the certificate ofincorporation document) to the entity record to replace the old valueand add a lineage entry.

Reporting and Compliance

In some embodiments, once any core record is recorded, entitystakeholders can receive reports about many aspects of the entity. Thesecan be simple event reminders such as a looming 83(b) filing deadline oras complex as creating the representations and warranties during amerger and acquisition. A non-trivial example of reports are the stockledger and capitalization table. Because the system captures founderstock grants, preferred shares (via financing) and stock option plangrants, it has all of the information required to compute both of thosereports.

The system may also use a scheduler to run periodic tasks to enforceactions required by the legal framework of the entity or to notifystakeholder of certain events, in some embodiments. For example, thesystem could start an employment agreement renewal process when itdetects that a contract is running out in the near future.

One of the benefits of the reporting capability is the ability toenforce contractual obligations. By way of example, an investor usuallyhas certain information rights, which are memorialized in documents suchas an investor agreement. Embodiments of this system and method storethese required representations in a computer-processable form, whichallows founders and other stakeholders to abide by representations,warranties, obligations and so on set forth in documents of the entity.This capability enhances the overall value of the entity.

The system also stores information for the entity itself. Another aspectof compliance is the enforcement of proper procedures when coreinformation about the entity is changed. The system associates a uniqueprocess with any field that requires documentation and approvals. Forexample, if the company needs to increase the amount of authorizedshares, shareholder and board approval is needed for an amendment to thecertificate of incorporation.

Because all processes in the system are modeled using standard workflowand business process tools, it is possible to create visualrepresentations in the form of flowchart images, i.e., the changeauthorized shares process. Those images can be used to demonstratecompliance with federal and local laws (for example, Sarbanes-Oxleycompliance) as well as industry standards such as the ISO 9000 family ofquality management standards.

Analytic Decision Support

A central goal of the system is to empower a user acting on behalf ofthe company to be able to execute common processes without needing legalsupport for simple information. In some embodiments, a decision supportengine uses analytics to provide decision support. For example, decisionsupport may be provided through the use of analytic trending capturinghow other users have chosen values for legal terms in processesperformed within the system. This trending information can help a userunderstand common selections. In order for the trending information tobe used effectively, it may be accompanied with context to describe whatis being presented as well as information describing what kind of datawas captured to create trust. Exposing term values with frequency ofusage will create a market of terms since it will be clear how and whencertain values are being used.

The algorithms and techniques used to provide a confidence assessment oftrending information can provide decision support as users executeprocesses within the system. For example, law firms provide trendinformation to their clients based on their experience, and in someembodiments, this system can quickly provide similar trendinginformation in the context of a specific decision across multiplecompanies. Summary trend information can be dynamically filtered by manydimensions, including time, geography, industry, maturity oforganization, confidence of organization and more. This information isonly available because the system is summarizing the execution of theseprocesses within the system and the user can decide the level ofconfidence desired from this trending information.

Another source of analytic decision support comes from the summarizationof historical actions undertaken by an individual or an entity. Sincethe system provides standard templates and many of these documents areexecuted many times in different contexts it is helpful to be able toexpose information about which version of a term a user or entity hasaccepted in the past. If an investor is negotiating a convertible notewith an entrepreneur, it is helpful for the investor to understand thatthey have accepted the exact form of the expenses provision five timesin the last year. Such information can avoid unnecessary negotiationsthat would otherwise drive up the costs of the financing. Similarly,maintaining metrics about previous history of executed terms that anentity has previously accepted helps focus attention to what's differentand more important to the different parties.

Confidence that data in a particular document is genuine and valuablefor trending could be based on but is not limited to:

-   -   Document execution confidence—prior to execution, a user can        certify her account as genuine by connecting to her social        profiles and authenticating email addresses. Corporate domain        verification may also be used, i.e., an email domain name may be        checked against a known email domain name to verify that a given        user has an address with a certain entity.    -   Entity certification—the system checks that the entity name is        registered with appropriate agency, officers are certified        system users with certified email addresses of the entity, and        the company has been verified by a trusted third party        organization.    -   Document source—represents a flag indicating whether the        document was uploaded and information manually added or        generated by the system during the course of execution.    -   External authority verification—an indicator whether the        document been audited and certified by a trusted third party.        This could be but is not limited to a lawyer or firm verified by        the system, a financial institution, auditing organization or        government agency.

Education

One of the primary features of the system is to provide transparency tocorporate governance. The goal is to not only handle processes anddocumentation for corporate leadership, but to educate all parties to anagreement about the processes so that they understand the rights andobligations the documents impose.

One step towards this goal is to break up the processes into small,understandable steps. The system provides “wizards,” or directedexploration tools, to clearly outline each step of a process. Each stepin the process in turn contains help text that explains its purpose. Anytechnical option or term is explained through contextual help.

In addition to contextual help, the system provides detailed help ondocument contents. Document templates are marked up with non-legalexplanations of each section within a document. The terms and theiroptions are explained with additional help steps so that the userunderstands each term and its consequences. The system also providescommenting functionality allowing users to discuss different options forterms and their legal implications. In addition the administrator canset entity-wide defaults options easing the decision for the user.

The system may provide statistics on the usage of terms in documents(where the word term encompasses the meaning of entire clauses withincontractual agreements, as well as its other meanings, including singlewords), giving the user an indication of the most commonly used ones aswell as inform the user of unusual selections. Should the user beconfused by anything, links are provided to ask counsel to review agiven term.

Legal Execution Framework Driven by Entity Records

Entity records are schema-defined data sets mapped to the keyinformation necessary to execute external and internal corporate actionsundertaken by the system. Changing this key information is governed bydifferent rules as to who can initiate such a change and the set ofapprovals and processes that may be followed to execute the task. Thissystem is configured to control access to view entity records values andto attach a process to each value of an entity record that controlsmodifications to it. These processes guide the initiating stakeholderand execute the appropriate legal processes by gathering informationfrom stakeholders, generating documents, gathering signatures andexecuting governing approval processes, e.g. Board and shareholderapprovals. The system is then configured to execute processes based onthe current status of the entity records.

In the example of Delaware corporate execution, the important entityrecords define the membership of the board of directors and stockholdersand how these bodies execute approvals. The board of directors entityrecord captures the members of the board and definitional datadescribing how it operates. This includes but is not limited to userinformation about each member, roles of each member as well as how manymembers are allowed, number of members needed to reach a quorum for ameeting, and more. The capital structure of the company is captured byentity records defining the different classes of stock, how the classesof stock interact for control and voting. For voting consideration, thestructure could have all classes converted to common stock and vote as asingle class or each class could vote separately. Once the classes forvoting are defined, the entity records can capture how the stockholdersvote. This entity record information for voting is leveraged as part ofprocesses to automate the execution and approval capture from the boardof directors and shareholders.

Once any necessary entity records to define corporate execution arecomplete, the system can expose processes executing withlegally-effective required approvals rather than manual input to changevarious other entity records. For example, if the company needed toincrease the number of authorized shares of the company, there is aspecific change authorized shares process to execute within the system.To perform this change to the entity record requires board andshareholder approval, as well as an amendment to the certificate ofincorporation that may be filed with the Delaware Secretary of State. Toexecute this process, the process may gather information from theprocess initiator (the user who initiated the process) to create corerecords. Those core records are used to generate the amendment documentthat may be filed and the board and shareholder resolutions that may beapproved. Once the process owner decides to execute this change, thesystem may help automate approvals. The entity record modificationprocess may block until both board and shareholder approvals aregranted.

The shareholder approval may be performed based on entity recordsdefining how such a vote may be executed and may send electroniccommunication, for example e-mails, and may require stakeholders to signa consent document. Alternatively, the process owner can decide to havea shareholder meeting and submit minutes to the system indicating thatthe resolution was approved. The board approval of the resolutions canalso be achieved by consent or through a board meeting and are executedbased on the entity records defining the process or a choice made by theprocess initiator. Once both approvals are received the original changeprocess is unblocked and the amendment can be filed with the state ofDelaware. The system may guide the user on how to file and requestevidence of the filing. When the process is complete, the system mayhave captured the documents and approvals with appropriate relationshipsand update the entity record with its new value along with the lineageto the documents that define the change.

As fields in the entity records are filled out, the system exposes newprocesses to be available to the company. For example, a process tocreate a stock incentive plan may reserve shares of common stock toenable the company to issue stock options to employees. Creation of sucha stock incentive plan requires information input from a corporateofficer (the user that initiated the process) that define the corerecords to generate the stock incentive plan document. These corerecords are also used to generate board and shareholder resolutions thatmay be approved by the board and stockholders as defined by thecorresponding legal process. Once the approvals are gathered, the systemtags the documents as approved, pushes relevant core records from thedocuments into entity records that track all stock incentive plans. Thesuccessful execution of creating a stock incentive plan now enables theentity to execute processes related to granting stock to employees andconsultants pursuant to the approved plan. These processes may read theentity records to make sure legal restrictions are maintained. Forexample, the number of shares grantable under the plan are limited andthe process may use analytics to calculate how many shares have alreadybeen granted to ensure that there are enough available shares for a newgrant. If not, the system may provide the user with a link to execute aprocess to create a new plan or increase the number of shares in theoriginal plan. Such a process may require board and shareholder approvalas defined by Delaware corporate law.

When a change to an entity record is made directly, the system may havea process to point the user to the necessary documents, approvals andfilings that may be made to execute a change. The system leverages otherentity records to guide the user and help automate the generation ofnecessary documents, gathering of approvals, execution of filings andthen actually execute the entity record value change. For example, tochange the number of authorized shares in a Delaware corporation today,the process must guide the user to provide the data needed to createcore records to generate an amendment to the certificate ofincorporation, generate board and shareholder resolutions and automatethe board and shareholder approval processes to then file the amendmentwith the state of Delaware. Once confirmation of a successful filing isreceived from Delaware, the system will execute the change to the numberof authorized shares of the company.

The system may allow stakeholders to delegate access to documents or toact on their behalf for a particular process or kind of process, e.g.,equity grants. An individual may decide they want to delegate theirexecution rights to sign personal documents to their lawyer. A corporateofficer may decide to delegate his or her signing authority for aparticular process to another officer. Since the execution of thatdocument within the process is performed in the same system that isstoring the delegation agreement, the system can track the lineage ofthe authority of the signature. This lineage can be done readily sincethe process, stakeholder rights, document generation and execution areall performed in one integrated system.

Processes

Processes for using the system described herein follow.

Processes for Entity Creation

In some embodiments, an entity may be created by the following process.A user, called the creator, may verify a security token, which may beprovided through an out-of-band channel before the user is permitted toproceed. Once the token is verified, the user may then be permitted tocreate an entity, create users, and show next steps for the entity. Theuser's user interface view may be redirected to the new entity.

In some embodiments, a new corporate entity may be incorporated by thefollowing process. The process may involve an incorporator and anadministrator, as well as the system. The administrator may begin theincorporation process and may select the incorporator. If theadministrator has prior-executed legal documents for upload, thosedocuments may be uploaded and key data contained in the document may bemanually entered via the user interface. In certain cases the documentsmay need to be re-signed, which can be performed on the system. If theadministrator is not the incorporator, the administrator may be directedto wait while the incorporator reviews and signs the documents. Once thedocuments are signed, the system may store the key data, including theregistered agent address and the incorporator address and thecertificate of incorporation terms, as core records on the respectivedocument and as entity records.

In some scenarios, if there are no prior documents, the key data may berequested by the system, such as the registered agent address and theincorporator address and the certificate of incorporation terms. Thesystem may then generate the certificate of incorporation, requestsignatures from any incorporators, and, once signed, await proof to bemanually input that the signed document has been filed with a stateauthority, such as the Delaware Secretary of State. The proof may be anuploaded copy of a signed and sealed document. The proof may be storedin the system with an evidence tag, for later retrieval and use. Thedate of the proof may be set as the incorporation date in the system forthe certificate of incorporation. All collected data is stored in corerecords of the generated documents and then also referenced in entityrecords. The incorporation using the document-generating path is nowcomplete.

Following incorporation, various processes may be performed, which mayinclude one or more of the following steps. An administrative user, whomay be the incorporator, may, using the system, define a board ofdirectors, assign corporate officers, define a set of founders, andgrant a stock distribution for the founders. Certain founders may bedesignated as vesting or non-vesting. Board members may be assignedspecific roles, including president, secretary, and treasurer. In thecommon case where the corporation has been incorporated by a soleincorporator, the system may then retrieve default data and determineany other data needed in order to generate a document, the consent inlieu of meeting of sole incorporator, for adopting bylaws, appointingdirectors, and performing certain other corporate functions as needed.The administrative user may be prompted for additional information andreview. A bylaws document may be generated at this time as well. If theadministrative user is the sole incorporator, he or she may review andsign electronically in the system. Otherwise, the document may besubmitted to the sole incorporator for review and signature.

Once this document is signed, causing the bylaws to be adopted and thedirectors to be appointed, additional documents may be generated. Usinginformation from the system about founders and authorized shares, andinput requested at this step from the administrative user, the systemmay generate a founder's agreement for assigning stock to each of thefounders. Using information from the entity record and from thefounder's agreement, the system may generate stock certificate forms forissuance of stock. Next, the system may use available informationregarding the founders' shareholdings to generate a founder's stockrestriction agreement. Next, the system may generate a consent in lieuof the first meeting of the board of directors for approving thefounder's stock restriction agreement, the stock certificates, the sharesubscription letter, and the founder's agreement. Next, the system mayrequest signatures from each of the directors. Once all documents aresigned, the documents may be updated with effective dates, and the sharesubscription letter vesting information may be updated. Finally, thesystem may await evidence that the founders paid to purchase theirshares of stock, upon which time the option exercise information isnoted as active.

General Corporate Processes

In some embodiments, when initializing the system, a user may becreated. If no user exists on the system, a user may be created uponsystem start. Alternatively, the manager may use a create user processto provision a new user. The manager or new user may initialize userdata such as username and email. The user is then sent an invitation byemail, and then asked to create a signature and fill out contactinformation.

In some embodiments, a user reset process may be performed by thesystem, which may include one or more of the following steps. The systemmay assign a new user as a performing user, or may have previouslyassigned the new user as a user. The system may send a reset email tothe user's email account, the email including a link for the user toautomatically access the system and/or reset his password. In someembodiments, secure authentication tokens, multi-factor authentication,and other authentication systems may be used to ensure that a user maynot access the system without due authorization.

In some embodiments, an add consultant process may be performed by thesystem, which may include one or more of the following steps. A managermay select a user to be identified as a consultant, and the system mayset the stakeholder as a consultant. The consulting agreement for theconsultant may be created from a document template, with the managerfilling in key data. Alternatively, the consulting agreement may beuploaded. Once the manager has reviewed, released, and signed theconsulting agreement, the consulting agreement may need to be approvedand signed by a corporate officer. The manager's status is thus checkedto determine if the manager is already a corporate officer, or ifanother officer is needed to approve. The system may send a welcomeemail to the consultant, with a link to create a user on the system. Theconsultant may then log in, update her address, create a signature ifnecessary, and sign the consulting agreement electronically, formalizingthe relationship. In some embodiments, when updating a prior consultingagreement, only the corporate officer, not the consultant herself, mayneed to sign.

In some embodiments, an add employee process may be performed by thesystem, which may include one or more of the following steps. A managermay select a person to be hired as an employee, and may identify amanager for that employee. The system may then set these parameters in aprocess being executed on the system. The system may then create aconfidentiality agreement, an offer letter, and/or other documents usingdefault values, including the person's name, title, and manager, asappropriate, and as previously identified. If additional key data orparameters are needed to complete the documents, they may be requestedfrom the manager. Alternatively, the confidentiality agreement and offerletter are uploaded. If the manager is not also a corporate officer, acorporate officer's signature is requested and obtained. Once the offerletter and confidentiality agreement are ready for the new employee, awelcome email is sent to the new employee, with a link allowing the newemployee to create an account, create a signature, and sign theemployment documents. The offer letter and confidentiality agreement areupdated in the system to reflect the corrected user data in the systemand to reflect the signature of the employee. Certain roles for theemployee take effect in the system once the employee has signed theagreements.

In some embodiments, an employee W-4 issuance process may be performedby the system, which may include one or more of the following steps. Anadministrative employee may start the process by selecting a documentsource, which describes whether the document is uploaded or generated bythe system, and an employee to whom a W-4 should be issued. The systemmay then request that the administrative employee check the addresses ofthe corporate entity and the employee in question. The system may alsorequest that the administrative employee indicate whether the documentwill be uploaded or should be generated by the system. Once theaddresses are checked, the system uses its database to retrieve otherrelevant information from the system, such as the W-4 employee's salaryand salary-related data, and the system may then generate the W-4.Whether generated or uploaded, the W-4 document is then presented to theadministrative employee for signing. The system notes the date when theW-4 document is signed. The administrative employee may be requested toreview and release the W-4 documents, at which a corporate officer maybe requested to approve the W-4 documents before they are sent out ordelivered.

In some embodiments, a create resolution process may be performed by thesystem, which may include one or more of the following steps. Acorporate officer may initiate the process, upon which the system mayinitialize a resolution document object with default values. Thecorporate officer may provide additional information, key data, and/orresolution metadata, which may be used by the system to generate aresolution document. The resolution document may be provided to thecorporate officer for approval. The same process may be used to createand approve corporate bylaws.

In some embodiments, a board resolution recordation process may beperformed by the system, which may include one or more of the followingsteps. One or more board resolutions may already have been created andmay be on the system. A board secretary may initiate the process ofrecording these board resolutions, at which time the system may simplymark the resolutions as approved in the system. In some embodiments, thesystem may also find a board meeting minutes document and update theboard minutes to reflect the approval of the resolutions. If the boardmeeting minutes do not exist on the system, the system may create aboard meeting minutes document using the relevant document template anddefault board meeting minutes metadata. The board secretary may bepresented with the board meeting minutes document for review, in someembodiments.

In some embodiments, a create meeting minutes process may be performedby the system, which may include one or more of the following steps.Once a board secretary initiates the process, the system may search foroutstanding but not completed board minutes, which may be a search forboard minutes for the most recent meeting. The system may then query theboard secretary to input key data regarding, e.g., the date of themeeting and/or what resolutions were passed, along with any other notesin a text format or any other format. If board minutes already exist forthe identified meeting, the changes may be merged with the existingminutes. If the board minutes reflect approval of any pendingresolutions, the resolutions may be marked in the system as beingapproved. The system may then generate a meeting minutes document forreview by the board secretary. Upon review and approval, the system maycreate a meeting minutes resolution to be approved and signed by theboard secretary and/or others.

In some embodiments, a create shareholder consent process may beperformed by the system, which may include one or more of the followingsteps. A corporate officer may begin the process by providing certainkey data, including a list of resolutions to include and a list ofshareholders to whom the consent should be sent. This set of designatedshareholders may be stored and used by the create shareholder consentprocess in order to generate shareholder consents to these shareholders.As the system has knowledge about each shareholder of the company, insome embodiments, the system may prompt the corporate officer to selectenough shareholders to achieve the consent of a majority ofshareholders. The shareholder consents may then be prepared for reviewby the corporate officer. Once the corporate officer has reviewed, theshareholder consents may be sent out via email for signature on thesystem. The corporate officer may monitor the signature process in realtime, i.e., may be able to access and monitor whether a shareholderemail has been sent, whether the shareholder has read the email, whetherthe shareholder has clicked the link to the system to read the attachedconsent document, whether the shareholder has read to the end of thedocument or what percentage of the document has been read, whether theshareholder has signed the document and what percentage of the documenthas been signed, and what number of signatures have been received andwhat number is outstanding. This signature process monitoringinformation may be made available in any or all of the processesdescribed herein, or in another process. Once the signatures arecollected and the shareholder consent is effective, the system may setthe effective date, mark the shareholder consent as active, mark theaffected resolutions as approved, and mark the affected resolutions asactive.

Although not every shareholder must consent to pass corporateresolutions, every shareholder has the right to be notified of suchresolutions. In some embodiments, a create shareholder communicationprocess may be performed by the system, which may include one or more ofthe following steps. A corporate officer may create a shareholdercommunication, which may involve inputting key data. Alternately, thecorporate officer may upload an already-created shareholdercommunication document to the system. The uploaded document may bescanned for metadata and data. In some cases, shareholder consents maybe tagged as communicated. If the corporate officer indicates thatemails should be sent, or if a setting has been previously made to sendemails regarding shareholder communications, individual emails may besent to each shareholder containing the content of the shareholdercommunication.

In some embodiments, a create board consent process may be performed bythe system, which may include one or more of the following steps. Amanager may input a list of resolutions to include, which may becombined by the system with default metadata to generate a board consentdocument. The manager may review the document and then requestsignatures. The system may then email the directors to sign. The managermay monitor the signatures applied in real time. Once the requiredsignatures are retrieved, the system may set a consent effective date,activate the consent, set resolution approval metadata, and activate theresolutions.

In addition to creating documents incorporating the company, thecreation of a new bank account in the name of the company may facilitatethe issuance of stock. In some embodiments, creation of a new bankaccount may be initiated by the system, as follows. A bank may enablethe system to create accounts and to initiate transfers of funds amongaccounts, in some embodiments. For example, the system may send arequest to the bank electronically, including the name of the corporateentity. In some embodiments, the request may be part of the workflow orprocess that is invoked when the user requests the creation of a newcorporate entity. In other embodiments, the request may be invoked whena user specifically requests the creation of a bank account. In someembodiments, the user may specifically indicate which bank is requestedto be used for the new account. The request may be sent via the Internetusing HyperText Transport Protocol (HTTP), using JavaScript ObjectNotation (JSON), in some embodiments, or via another comparable methodthat is compatible with systems operated by the bank. The name of thecorporate entity may be retrieved from the document record for theincorporation document for the corporation. The identification of thespecific document record to be retrieved may be performed by theoperation of the workflow or process stored within the system, in someembodiments. Other information may be included in the request in someembodiments, such as the corporation's tax ID number (e.g., EIN) orother information as required by the bank. In some embodiments, the bankmay immediately acknowledge receipt of the request; in otherembodiments, the bank may respond only when the bank account has beencreated. Once the bank receives the request from the system to create anaccount in the name of the corporation, the bank may perform thenecessary steps to create the account, and may send a response back tothe system. In some embodiments, the response may include parameterssuch as the new bank account number in the name of the corporate entity,the routing number of the bank that relates to the new account, or otherparameters. The response may be in a similar format as the request,e.g., HTTP/JSON, or it may be via email, or via another means orprotocol.

Processes for Financing

In some embodiments, a create bridge note process, for convertible notebridge financing, may be performed by the system, which may include oneor more of the following steps. Interactions between corporate officers,purchasers, corporate secretaries, representatives, and the system maybe described. A corporate officer may select the create bridge noteprocess, fill out an investment questionnaire, and verify that thebridge note was not publicly solicited. The system may assignrepresentative participants and set certain metadata for the notepurchase agreement (NPA). The corporate officer may be requested toprovide additional key data at this time, including the purchasers ofthe notes. Once the purchasers are identified, the system may add thepurchasers and stock to the NPA metadata, and add the corporate officerto the NPA as the representative of the company. The system may thengenerate a term sheet.

Once the term sheet is created, the corporate officer may review andcollect approvals and signatures. The approvals and signatures may becollected via the system and the approvals may be monitored in real timeby the corporate officer or others. Next, a note form document may begenerated, and the note purchase agreement may also be generated. Thepurchaser is then asked to provide metadata for the notes, and thecorporate officer is requested to provide other note terms. The systemthen generates the note document, for review by the corporate officer.The corporate officer then selects shareholders to be requested toapprove the note document. The system then generates appropriate boardresolutions, shareholder communications, shareholder resolutions, and/orother documents for review and execution, which are then reviewed by thecorporate officer and then sent out for signature. The corporate officermay also then define representations and warranties for board andshareholder approval, and these disclosures may be added to the notepurchase agreement.

Once the approvals are received from board members and shareholders, atthis time, the bank wire information is added by the corporate officerand final review is performed by the corporate officer. Purchasers maythen be permitted to sign up, and representatives may be requested tosign. Once all signatures are in place from purchasers, the deliverablesmay be indicated as closed.

The certificate of good standing and corporate bylaws may be retrievedand used to generate a certification for the corporate secretary tosign. The corporate secretary may then be requested to sign. Thecorporate officer may then certify the closing conditions, and recordthe closing date in the note purchase agreement. The note purchaseagreement may then be marked as legally active in the system and thenotes updated with the closing date and marked as legally active in thesystem.

Processes for Stock Grants

In some embodiments, a create stock plan process may be performed by thesystem, which may include one or more of the following steps. Acorporate officer may begin the process by selecting a grant type. Thesystem may then present the metadata of the corporate entity to thecorporate officer for confirmation/review. The corporate officer maychoose one or more grantees, and provide key data and grant terms forthe stock grant, upon which the system may generate a grant documentbased on the provided data, on a document template, and on priordefaults for the entity. After the grant document is generated, thecorporate officer is requested to check any constraints that may pertainto the corporate entity, such as whether sufficient authorized sharesremain for the stock grant, and to review the stock grant document. Thesystem may also search for a fair market value resolution for thecorporate entity. If there is no fair market value resolution, thesystem may generate a document for a fair market value board resolution.The system may also search for a board resolution or board resolutionexhibit regarding an incentive stock option grant plan. If no such planor exhibit is found, the system may generate a board resolution documentfor an incentive stock option grant plan, to be approved by the board,with information pertaining to the new stock grant. If more than oneplan is found, an appropriate plan may be selected. Once an appropriateplan is found, the plan may be updated with information pertaining tothe new stock grant. If the grant plan execution board resolution hasnot been previously executed and/or a board resolution for grant plancertificate cannot be found, the system may generate an execution boardresolution, and generate a board resolution for a grant plancertificate. The approval status of the stock option grant may now bepresented to the corporate officer. If the corporate officer agrees witheach of the documents, the corporate officer may sign the grant documentand other documents. If the corporate officer decides that certain boardresolutions need to be passed first, the corporate officer may be ableto perform the relevant board resolution approval processes on thesystem. Once the grant document has been signed, the system waits forthe grantee to sign onto the system and accept the grant, at which timethe grant is active.

In some embodiments, an employee stock plan grant process may beperformed by the system, which may include one or more of the followingsteps. A corporate officer may initiate the process and may select agrant type. The corporate officer may be prompted to check the addressand other data pertaining to the corporate entity and the grant, and tochoose the grantee, who may be a user on the system, and may be promptedfor additional information regarding the grant terms, such as a numberof shares authorized for grant, a vesting period and/or cliff, the typeof stock (i.e., restricted or non-restricted), or other terms. Thesystem may check to ensure that the total number of authorized shares isnot exceeded, and may check other constraints as needed. The system maythen generate the grant document. The corporate officer may then reviewthe grant document for errors and approve the document. The system mayalso search for a fair market value resolution for the corporate entity.If there is no fair market value resolution, the system may generate adocument for a fair market value board resolution. The system may alsosearch for a board resolution or board resolution exhibit regarding anincentive stock option grant plan. If no such plan or exhibit is found,the system may generate a board resolution document for an incentivestock option grant plan, to be approved by the board, with informationpertaining to the new stock grant. If more than one plan is found, anappropriate plan may be selected. Once an appropriate plan is found, theplan may be updated with information pertaining to the new stock grant.If the grant plan execution board resolution has not been previouslyexecuted and/or a board resolution for grant plan certificate cannot befound, the system may generate an execution board resolution, andgenerate a board resolution for a grant plan certificate. The approvalstatus of the stock option grant may now be presented to the corporateofficer. If the corporate officer agrees with each of the documents, thecorporate officer may sign the grant document and other documents. Ifthe corporate officer decides that certain board resolutions need to bepassed first, the corporate officer may be able to perform the relevantboard resolution approval processes on the system. Once the grantdocument has been signed, the system waits for the grantee to sign ontothe system and accept the grant, at which time the grant is active.

In some embodiments, a change authorized shares process may be performedby the system, which may include one or more of the following steps.First, a manager initiates the process, in some cases providing keydata. The manager selects shareholders to be affected. The system thengenerates a board resolution document based on the provided key data, ona document template, and on prior defaults for the entity. The systemthen generates a shareholder resolution document and a shareholderconsent document using default metadata. The documents may then be sentto a manager for review. Upon approval of the documents, allshareholders may be automatically sent emails to request theirelectronic signature, and the manager may monitor the status of how manysignatures have been collected in real time. Shareholder approvals mayalso be tracked using the application of tags or other metadata. Onceall needed signatures are obtained, the system may find thecorporation's certificate of incorporation and generate an amendmentdocument to amend the number of authorized shares. The document is thensent to the manager for signature. Certain evidence may be required bythe Secretary of State of a given jurisdiction, such as a copy ofprior-filed articles of incorporation, and these evidentiaryrequirements may be met by retrieval of stored documents in the system.The system may then prepare these documents for submission to theSecretary of State, or submit these documents to a third party ordirectly, and may subsequently update the number of authorized shares inthe system.

In some embodiments, an employee stock option exercise process may beperformed by the system, which may include one or more of the followingsteps. A user, called the grantee, may initiate the process, and thegrantee may then be asked by the system how many options she would liketo exercise, along with any other key data. Upon receiving thisinformation, the system generates an exercise notice document. Thesystem may also determine whether the grantee has any unvested shares,and whether an early exercise clause is permitted, e.g., via a clause inthe corporate entity's incentive stock option plan. In the case that thegrantee has unvested shares, the system may generate a restrictiondocument providing conditions over the grantee's option exercise. Oncethe document or documents are generated, they may be presented to thegrantee for signature. The grantee may then be requested to provideevidence that payment was properly tendered to the corporation for theshares. Alternately, a direct electronic payment may be initiated by thesystem using payment data provided by the grantee, or the grantee may beredirected to another system to cause the electronic payment to occur.Once payment has been established, the system may set the exercise dateof the options and may present the exercise to a representative of thecorporate entity for approval, which may be another user. Once approvalis granted by the corporate representative, the exercise notice may bemarked approved, a stock certificate may be generated, and signaturesmay be requested from the corporate entity's president, board secretary,or any other persons or users as appropriate. Once the certificate issigned, it may be marked as issued and the grantee may be notified.

In some embodiments, an employee stock option Rule 83(b) electionprocess may be performed by the system, which may include one or more ofthe following steps. The Rule 83(b) election process may be initiatedautomatically at the conclusion of the issuance of stock or exercise ofoptions to a grantee. When an employee initiates the process, the systemmay obtain entity metadata from a particular company that the employeebelongs to. Next, the system may fill out default values for a Rule83(b) election document. The system may determine whether the employeehas an explicit exercise at this time, and if the answer is yes,information from the exercise may be imported into the process. Theemployee may then be asked for key data regarding the Rule 83(b)election, as needed based on a template, and the system may then createthe document from the document template. The employee may then berequired to electronically sign. The employee may then be required tosend the document to the Internal Revenue Service, and once completed,upload evidence that the document has been filed to the system, at whichtime the mail date of the document is updated to the appropriate dateand the document is set to active status. The evidence may be taggedwith an evidence tag, and the evidence and the Rule 83(b) document maybe related with an evidence relationship. Alternatively, the employeemay be given the opportunity to upload an existing Rule 83(b) electiondocument, and, if necessary, to re-sign the document.

In some embodiments, a fair market value setting process may beperformed by the system, which may include one or more of the followingsteps. According to Section 409A of the Internal Revenue Code, stockoption grants have an exercise price at or above the fair market valueof the company's common stock on the date such grant is made. The fairmarket value of a company's stock may be established by a company'sboard of directors. A corporate officer may start the process byselecting a corporate entity and/or a document source. The system maysearch for any existing fair market value board resolution, as well asany default board resolution values, for use in determining key valuesfor a new fair market value board resolution. The corporate officer maybe prompted to indicate whether a new document should be generated orwhether an existing fair market value resolution is to be uploaded. Ifthe corporate officer chooses to upload an existing fair market valueresolution, the system may update the fair market value for the entityusing the uploaded document as the source document for the fair marketvalue core record. Any prior fair market value board resolutions may bemarked inactive.

If the corporate officer chooses to generate a new fair market valueresolution, the corporate officer may be prompted for additional keydata, after which the system may generate a new fair market value boardresolution pursuant to Internal Revenue Code Section 409A. However, onits own, the board resolution is not sufficient to set the fair marketvalue of the corporate entity. Under IRC 409A, “safe harbors” exist fora new company or for a company that relies on a valuation from a thirdparty firm meeting certain objective standards. In many circumstances, asmall business or startup may wish to rely on these safe harbors toreduce administrative burden as well as risk. The system may permit anentity wishes to rely on these “safe harbors” by prompting the corporateofficer to upload proof that such a valuation has occurred. One or moredocuments may be uploaded to the corporate data store for compliancewith any future audit.

Once one or more documents are uploaded to establish the corporateentity's compliance with IRC 409A, the corporate officer may be promptedto review and release the new fair market value board resolution to theboard. The board resolution may be sent to the other board members forapproval, during which time the corporate officer may monitor theapproval status of the board resolution. Once a sufficient number ofboard members have approved the new board resolution, any prior fairmarket value board resolution is marked as inactive, the new fair marketvalue board resolution is marked as active, and the fair market value ofthe shares of the corporate entity are stored in the system, with thesource of the fair market value being identified as the fair marketvalue board resolution.

Processes for Bank Transaction Facilitation

In some embodiments, the system may be enabled to initiate transfer offunds from each of the recipients of a stock grant to the company's bankaccount, in some embodiments. Initiating transfer of funds in this waymay be performed as follows. According to the operation of a workflow asdefined by the system, a recipient of a stock grant may be notified thathe or she is required to make payments to the company in order topurchase the stock grant, in some embodiments. In some embodiments, thenotification may be omitted. In some embodiments, individual granteesmay specify their preferences and/or information about the bank accountswhich they hold, in order to enable the transfer of funds. In otherembodiments, the grantees may be enabled to notify the system when thefunds have been transferred. When the workflow is configured to requestinformation about bank accounts directly from grantees, the system mayuse the information received from the grantees about their personal bankaccounts, together with information about any bank accounts in the nameof the corporation, including bank accounts created at the initiation ofthe system, to request, of the bank, a transfer of funds from eachgrantee's bank account to the bank account of the system, in someembodiments. The workflow may be configured to retrieve, fromappropriate document records defined by the workflow, the initial stockprice or relevant option price of the corporation and the number ofshares/options being transferred. The workflow may then multiply theprice with the number of shares and/or options, and may then request thetransfer of the appropriate amount of funds from the grantee's accountto the corporation's account from the bank, in some embodiments.

The transfer of funds may be specifically authorized by the granteesusing the system, in some embodiments. In some embodiments,cryptographic security may be employed between the system and the bank'ssystems. In some embodiments, cryptographic signing may be used toauthorize the system to perform the transfer. In some embodiments, theauthorization may take the form of a document, and may be stored as adocument record in the data store, with the document records includingvarious entity records including the amount authorized, the bank accountnumber of the grantee, the bank account number of the grantor (i.e., thecorporation), and/or other entity records.

In some embodiments, employees may exercise options or purchases ofstock or restricted stock awards (RSAs) by authorizing the system toperform purchases by automated clearing house (ACH)/wire transfer. Insome embodiments, an investor as part of note or equity financing may begiven the opportunity to approve wires as part of signing of a stockpurchase agreement. In other embodiments, wires may be configured totrigger automatically upon deal close, according to workflows. In someembodiments, whether approval is required may be determined using aworkflow. In some embodiments, a shareholder may be enabled to initiatea Sale of Stock workflow. The Sale of Stock workflow may initiate adirect transfer of funds via ACH or wire to the stock seller's account.In some embodiments, investor capital calls may be handled through thesystem and wires automatically initiated based on pre-agreed upon dollaramounts, which may be stored in entity records and associated withdocument records. In some embodiments, the system may have the abilityto verify payment by looking for received funds in corporate account,and/or the ability to verify repurchase payment by looking at outgoingtransfers from company to shareholders.

In some embodiments, for one or more of the processes above, a managermay be asked to select a document source specific to a particularcorporate entity, or to enter or select entity metadata. This may occurin particular when a user has a manager role for more than one company.

In some embodiments, generation of a document may be based on key datareceived from a user, system-wide defaults previously stored in thesystem, defaults previously provided for the entity or process type,and/or on a document template, in addition to the parameters describedabove. In the description above, the term “key data” refers to some orall data or information relevant to a given process.

In some cases, one or more of the relevant persons for a given process,apart from the initiating or controlling user, may not be a user on thesystem. Some embodiments may permit non-users to participate in theprocesses described herein by the use of ordinary paper documents forreview and approval, where these documents may be generated by thesystem. A user of the system with administrative approval, or acorporate officer, or any user, may upload evidence of the review and/orapproval of a document to the system where appropriate.

In some embodiments, each of the preceding processes may include one ormore steps from other processes described above, or steps from otherprocesses or steps not described, in any order. Each of the precedingprocesses may be broken into multiple processes or combined.

Drawings

FIG. 1 shows a network diagram of a platform for providing the servicesdescribed herein, in accordance with some embodiments. Businessoperating system platform 101 may include load balancer 102, app tier103, queue tier 104, worker tier 105, database tier 106, authenticationtier 107, document signing tier 108 and messaging tier 109. Each tiermay include one or more servers that may be virtual servers or physicalservers. The servers may be activated or deactivated as needed based onload parameters that may be determined by the business operating system,wherein the load parameters include CPU load and network bandwidthutilization.

Load balancer 102 acts as a gateway between the remainder of platform101 and the public Internet, in some embodiments. Load balancer 102 alsomay allocate incoming requests among servers in app tier 103. In someembodiments, an HTTP load balancer such as nginx may be used.

App tier 103 includes one or more web servers 103 a, 103 b for receivingweb requests via Hypertext Transfer Protocol (HTTP), in someembodiments. The web servers may then determine what tasks, if any, needto be distributed to either a database tier 106 or a queue tier 104. Theweb servers may then return fully- or partially-rendered web pages to arequesting web browser. As the web browsers are behind load balancer102, different servers may service different web requests. In someembodiments, the web servers may be web application servers, and theapplications running on them may be precompiled, linked at runtime,Common Gateway Interface (CGI) applications, modules executed by a webserver process, or otherwise executed. The web servers may alsointegrate their own load balancing, in some embodiments. In someembodiments, load balancing may occur only at 102, only at 103, or atneither, or both points in the system.

The queue tier 104 and the worker tier 105 may include one or moreservers, and may include a facility to activate or deactivate servers asneeded to meet the needs of the service, in some embodiments. The queuetier 104 may receive requests from the app tier 103 and may identifysub-tasks, which may then be sent to worker tier 105 to be executed. Thequeue tier 104 may use a queuing messaging protocol such as RabbitMQ forassigning tasks to processes at the worker tier, in some embodiments.The queue tier 104 may use the Celery queuing software with well-knownqueuing algorithms to provide reliable service.

The worker tier may execute sub-tasks, such as rendering documents,executing processes, requesting data from database tier 106, and sendingemails, in some embodiments. The sub-tasks may execute at the workertier as threads, processes, or via another processing abstraction thatis capable of being processed in parallel. The sub-tasks may involve oneor more requests for data from other servers or network nodes. Renderingdocuments may cause portions of documents to be rendered to text,Hypertext Markup Language (HTML), partial HTML (HTML snippets),JavaScript, JSON, Portable Document Format, the ReportLab report markuplanguage (RML), or another format. Rendering documents may also involvecombining data stored in core records with data stored in or generatedby document templates, as described above. In some embodiments, reports,including reports generated by ReportLab from RML, and including auditreports and logs, may be generated. In some embodiments, documents maybe generated based on user input and then sent back to the app tier 103for authentication by the authentication tier 107.

Execution of processes may involve the use of processes stored aseXtensible Markup Language (XML), XML process definition language (XPDL)workflows, or other data that define the process, and may involve thecreation of or modification of entity records, core records, stakeholderrecords, or other records. Emails may be sent by the worker tier to, forexample, send reminders about approaching deadlines or to send passwordreset messages. When worker tier 105 completes work and/or receives anappropriate response from one or more other servers, it sends a message,which may be HTTP JSON, to a messaging tier 109, which is responsiblefor assembling a reply and sending it back to a requesting user via loadbalancer 102.

Database tier 106 may receive requests for data from worker tier 105,and may retrieve information stored in the form of one or more corerecords, entity records, or stakeholder records. Data may be written toone or more databases as serialized JSON objects. The database tier 106may use a database that enables JSON storage, such as PostgreSQL 9.4 orabove using the JSONB data type. Data from multiple entities may bedistributed across database servers in various ways. In someembodiments, all data for a particular corporate entity may be placed ona single database server, enabling sharding of large databases on aper-entity basis and providing added security for each entity. Data maybe requested from the database tier by a worker tier or by the app tierdirectly. When data is needed to perform a task or sub-task, in someembodiments, the worker tier may cause data to be retrieved from thedatabase tier. In other embodiments, the queue tier may create dataretrieval requests from the database tier, or both the queue tier andthe worker tier may send requests to the database tier. When data iscreated by the worker tier, for example, an HTML snippet, a complete PDFfile, or a new or modified entity record in a corporate entity, data maybe sent to and stored in the database tier 106 as JSON. In someembodiments, a cache or alternative data structure server such asmemcached or Redis may be used for improving the read/write performanceof database tier 106.

Also shown are authentication tier 107 and document signing tier 108.Authentication tier 107 serves to identify whether the logged-in userhas the proper credentials to perform a particular process or sign aparticular document. Authentication tier 107 may use the lightweightdirectory access protocol (LDAP) within an organization, or using anLDAP server (not shown), to authenticate a user. Authentication tier 107may use the Red Hat FreeIPA suite, which includes LDAP, for managingidentity, policy, and audit functions, including for keeping an auditlog. Authentication tier 107 may also use Kerberos to permit users andother nodes securely prove their identity, or to securely prove theidentify of the platform to external providers. Authentication tier 107may permit the use of two-factor authentication. Document signing tier108 may be responsible for communicating with a third-party system, suchas GlobalSign, to cause the third-party system to use aroot-authenticated certificate to cryptographically sign the documentafter it is finalized, using Adobe Certified Document Services (CDS), toprevent modification of the document. The cryptographically-signeddocument may be saved to database tier 106 as a PDF associated with adocument object.

Document signing tier 108 may use a Java library to communicate with asecure signing service located at an external network provider. Documentsigning tier 108 may include modules for interpreting both Java andJSON, for communicating with services internal to system 101.

One or more of the above application servers, web servers, loadbalancing servers, database servers, or other servers may be running aLinux operating system. In some embodiments, when used in a productionrole, the servers may be configured to have a minimum of servicesactive, excepting only the specific services described above. This hasthe advantage of increased security, which is desirable when performingcorporate processes and providing secure authentication services. Inother embodiments, the servers may have additional active services. Insome embodiments, a virtual private network (VPN) server 111 may providethe sole connection to the outside Internet for the system, therebyacting as a security gateway. In other embodiments, users may connectdirectly via network 110 to the system. Whether or not a VPN is used asa security gateway, access to applications may be limited through theload balancer as a gateway.

In some embodiments, one or more of the servers described may operateusing the Linux operating system, and/or using an Ubuntu distribution ofLinux. Various messaging protocols may be used between tiers, includingfor message passing; for example, RabbitMQ and Celery queuing andmessage passing middleware may be used. HTTP and JSON may be used asprotocols for transmitting data. The web servers may use webapplications written in Python in conjunction with a web server, such asthe Nginx web server. Caching may be performed at one of the app tier,queue tier, or database tier using a web cache or object cache such asRedis. Servers as described herein may be virtual servers. Access to theplatform may be partially limited to or solely through a virtual privatenetwork (VPN).

FIG. 2 is a schematic diagram of an application server, in accordancewith some embodiments. Application server 200 may be an applicationserver, or a group of application servers, such as the app tier 103shown in FIG. 1. Application server 200 includes a business operatingsystem 201, which further includes business logic 202, signature manager203, security manager 204, document templates 205, entity record schemas206, stakeholder record schemas 207, process execution engine 208, anddecision support engine 225. Business logic 202 may be one or morebusiness processes, configured to be executed by process executionengine 208. Examples of a business process are: incorporation;nomination of a board; creating board resolutions; creating a stockplan; granting stock to an employee; and identifying a consultant or anemployee, among other examples. Signature manager 203 may providefunctionality and services for storing electronic signatures, retrievingprior-stored signatures, and reading and writing quick response (QR)codes. Security manager 204 may provide functionality pertaining to thesecurity of the system, such as logging, transaction monitoring,authentication and authorization, auditing and reporting, as well asinterfacing with third-party security functionality and services.

Document templates 205, entity record schemas 206, and stakeholderrecord schemas 207 provide the framework for data to be stored on thesystem. Document templates 205 provide templates for a variety of typesof documents. As the documents are intended to be legal documents for acompany's business processes, some or all of the document templates maybe authored by attorneys according to state and federal law, withparticular attention to Delaware corporate law. The document templatesmay be predefined and inalterable, or they may be alterable such that acompany may make changes to the document templates by uploading newtemplates, or the document templates may be individually alterable. Theentity record schemas 206 may include schemas for various types ofcorporate entities, such as S-corporations, C-corporations, limitedliability corporations and partnerships, and may include parameters suchas state of incorporation, address of incorporator, address ofcorporation, primary address, board membership, corporate structure, andother parameters. The stakeholder record schemas 207 may define astakeholder as a person within the context of the entity, with contactinformation for the person such as address, email address, and phonenumber(s), and may also define a stakeholder as having one or moreroles, such as board member, board secretary, shareholder, corporateofficer, or other roles. A single stakeholder may hold more than onerole; a user may also hold one or more roles for one or more corporateentities.

Decision support engine 225 may provide analytics for real-timereporting during the execution of a business process, based on dataavailable to the business operating system. For example, if multiplepeople known to the business operating system have the title “ChiefEngineer,” the system may be able to compute basic analytics on this setof people to provide information regarding their average and mediansalary, stock compensation, etc., in real time such that at the time anew hire contract is being created on the system, the relevantinformation is provided to the user. Decision support engine 225 mayrely on external document storage 222 for this information, and may alsorely on business logic 202 and process execution engine 208 to determinewhen the decision support engine 225 may be invoked.

Application server 200 may interact with external document storage 222via network 224 a. In some embodiments, external document storage 222may be for storing generated documents in binary format only, such thata user may be able to retrieve relevant legal documents at any timewithout use of the business operating system 201. The external documentstorage provider may be, for example, Box.com, Dropbox, Google Drive, aprivate WebDAV file store, or any other cloud-based content storagesolution. In other embodiments, external document storage may be usedfor storing all information, including information formatted accordingto document templates 205, entity record schemas 206, and stakeholderrecord schemas 207. Application server 200 may also interact withexternal authority 223 and users 225 a, 225 b, 225 c via network 224 b.An external authority 223 may be provided for authenticating users onthe system. For example, an external authority may provide two-factorauthentication support such that a user may be authorized by theexternal authority before being granted access to business operatingsystem 201. Graphical user interface 209 may provide a visual interfaceto business operating system 201; the user interface 209 may appear in aweb browser and may combine results and outputs from multiple parts ofbusiness operating system 201 into a single outputted HTML page. In someembodiments, the HTML page may contain functionality as well, such asinput validation functionality performed in JavaScript, in order toprovide higher-quality data to the underlying system.

FIG. 3 is a schematic diagram of a database server, in accordance withsome embodiments. Document 310 includes core records 311, binary filedata 312, report card 313, and tags 314. Entity record 315 includescurrent value 316 and lineage entry 317, which includes old value 318,new value 319, timestamp 320, and value source 321. Stakeholder record322 is also shown. Each of the above data objects is stored in adatabase at a database server, and may be stored in a relationaldatabase, such as PostgreSQL, in a non-relational manner, such as in theJSONB format. In some embodiments, data elements may comprise referencesto other data objects. For example, the binary file data 312 in document310 may be actual binary file data stored in a database, or may be areference to binary file data stored outside of a database, for example,as a uniform resource indicator (URI) indicating the location of a fileaccessible via HTTP from another server. Also, the value source 321 thatis part of lineage entry 317 may be a reference to another object, suchas another document object, and may not be the object itself. In someembodiments, an array of lineage entries may be stored in entity record315.

Document 310 is intended to permit multiple core records 311 to beassociated with the document. For example, a certificate ofincorporation would have at least a core record for the company'saddress and another core record for the founders of the company. In someembodiments, the report card may or may not be present; when present,the report card may be updated at the time the document object is savedor at a later time based on when processing resources are available forcalculating the trustworthiness of the data associated with thedocument. In some embodiments, a single binary file data object 312 isassociated with one document object 310. Documents may be associatedwith entity records as well, in some embodiments,

In some embodiments, tags 314 are free-form text and may behuman-readable. Multiple tags may be associated with a single document.In some embodiments, the tags may have a hierarchical structure tofacilitate search and retrieval. Certain tags may be special; forexample, the “active” tag indicates to the system that a document islegally in effect, and may be automatically updated when a new documentis created or when an older document is superseded; also, entity recordsmay be associated with documents as tags, in some embodiments.Superseding of a document may be quickly determined by the systemperforming a search for the type of document, e.g., “stock option plan,”to find all documents with a particular type for a particular entityrecord.

In some embodiments, an entity record 315 may include both a currentvalue 316 and a lineage entry 317. Although an entity record contains acurrent value 316, the entity record's current value 316 duplicates thevalue stored in the lineage entry. This facilitates retrieval of thevalue without dereferencing any references in the lineage entry, and maybe thought of as a cached value. Lineage entry 317 includes at least avalue source 321, to indicate that the lineage of the current value isoriginally from that other object. Lineage entry 317 may also includeold value 318, which is the value that was previously stored in theentity record; new value 319, which is the same as the current value 316and the value of that entity in value source 321; and a timestamp 320.Current value 316 may be thought of as a cached value. Current value 316points to an up-to-date value of the core record, even if the corerecord has been modified.

Value source 321 may be a reference to another object, such as adocument. For example, if a stock option plan was put into place at aprior date, the number of authorized shares of a corporation would bedetermined by the active stock option plan document, so although theentity record for the corporation would include the number of shares ofthe corporation, it would also indicate that the number of sharesoriginated in the active stock option plan document. An auditor wouldthus be able to determine the source of the number of shares upon laterreview.

In some embodiments, a value source 321 may be a stakeholder record andnot a document. This may occur when a value is manually entered withoutreference to a prior document, or when a document is uploaded and doesnot contain generated values in the system.

In some embodiments, stakeholder record 322 may include one or moreroles (not shown), as well as basic information about the stakeholder,such as name, address, phone number, email, and so on (not shown). Arole indicates what actions that may be performed or initiated by thestakeholder.

FIG. 4 is a schematic diagram of a data model, in accordance with someembodiments. In the scenario depicted in FIG. 4, an initial certificateof incorporation 403 has been superseded by an amendment 402. Stockincentive plan (“SIP”) 401 contains the up-to-date value stored in theentity record at the time the stock incentive plan 401 is made. Document403 is a certificate of incorporation, with core record 403 a thatfurther includes ci.name 403 b (“Acme”), source 403 c (“manual entry”),and timestamp 403 d. Document 403 also includes a type parameter 403 e(“COI”), and a status 402 f (“Inactive”). Document 402 is an amendment,with core record 402 a that further includes ci.name 402 b (“Acme,Inc.”), source 402 c (“manual entry”), and timestamp 402 d. Document 402also includes a type parameter 403 e (“COI”), and a status 403 f(“Active”), as well as a reference 402 g to certificate of incorporation403 (“base.derivedFrom: COI”). Parameter 402 g may be used foramendments, or for documents that derive from other documents,generally. Stock incentive plan 401 includes a core record 401 a thatitself includes entity.legal name 401 b (“Acme, Inc.”), reflecting thecorrected name in amendment 402, for the company name at the time thestock incentive plan document 401 is created. Core record 401 a alsoincludes source 401 c and timestamp 401 d.

It is noted that each of the documents 401, 402, 403 shown in FIG. 4 donot need to be modified after execution and finalization. As with paperdocuments, each document contains specific data that is only guaranteedto be valid at the time the documents are made. The entity recordcontains an up-to-date copy of the current information for the corporateentity, and references individual documents to enable auditing. Takentogether, the system may provide a cache of all information pertainingto the corporate entity valid at the present time; this information isderived from the documents stored in the document database. As part ofthe process that generates any new document, a system step may updatethe entity record as necessary. Specifically, the entity record may beupdated after approval and finalization of a document. As new documentssupersede old documents, those old documents may be marked inactive, andthe new documents marked active. At any time, a search on the status tagcan be used for retrieving all active documents for the corporateentity.

FIG. 5 is a schematic diagram of a document, in accordance with someembodiments. Document 310 includes section 501, which further includesterm 502, which itself further includes options, specifically, defaultoption 503, entity default option 504, non-default option 505, andcustom text option 506. Document 310 also includes signature block 507and report card 313. Term 502 may be a core record; each core record mayhave one or more default options, as shown in this figure. Defaultoption 503 may be a default value that relates to the specific corerecord type. Entity default option 504 may be a default that is specificto the entity record and may be stored or cached with the entity, insome embodiments. Non-default option 505 is a value that is not adefault option; in many cases, certain key data, such as a number ofshares to be created upon incorporation, may be requested from a user atthe time a process is performed, and such values may be stored asnon-default options. Custom text option 506 may be any other value,including a value that is known to take on one or more values from aspecific set of possible values, in some embodiments. Signature block507 will be described below at FIG. 13. Report card 313 includesinformation that may be used to perform an audit and/or assess thesubjective quality of values stored in document 310, and will be furtherdescribed below at FIG. 19.

FIG. 6 is a schematic diagram of a document template, in accordance withsome embodiments. Document template 602 includes core recordsdefinitions 604, which itself includes core record schema 606, whichincludes core record field 608. Document template 602 also includesdocument rendering instructions 610, rendering markup 612,document/rendering structure 614, and core record references 616.Document template 602 also includes business logic 618 and tags 620.

Document template 602 is a template used for generating a document usingthe system. Business processes stored in the system rely on one or moredocument templates to generate various different types of documents. Thedocuments themselves include sections, terms, and core values, asdescribed elsewhere herein and above regarding FIG. 5.

Document template 602 includes at least the following elements. First, adocument template includes a list of core records that are part of thedocument, which here are shown as core records definitions 604, corerecord schema 606, and core record field 608 (as well as core recordreferences 616). In some embodiments, the schema 606 is not stored withthe document template. The list of core records is an important part ofthe document. For example, an incentive stock option policy will havevarious parameters, including a number of options, a vesting schedule,the presence or absence of a vesting cliff, the presence or absence ofan early exercise clause, etc. These parameters should be written intothe document. The category of document template may define the set ofcore records in a document template, in some embodiments. Multipletemplates may be provided for any reason, including for providing fordifferent entities' preferred values.

Document rendering instructions 610 is the set of instructions and datathat, when combined with values corresponding to all key recordsassociated with the template, enable the system to generate a documentusing the document template, in some embodiments. In some embodiments,document rendering instructions 610 would include, for example,boilerplate text of an agreement and its formatting (as rendering markup612), a document structure, and references to the core records definedin core record definitions 604. Document rendering instructions 610 maybe used to render the document for viewing in the user interface, forrendering as HTML, or for rendering as a PDF file to be stored and/orprinted. In some embodiments, document template 602 may be an eXtensibleMarkup Language (XML) document, or may contain an XML document.

Business logic 618, in some embodiments, is logic that may be executedat the time a document is created using document template 602. Tags 620are general-purpose, freeform text that are used for storing varioussystem-wide information, such as document status (i.e., active orinactive), document type, and other parameters.

FIG. 7 is a schematic diagram of a core record, in accordance with someembodiments. Core record field 702 includes default factory 704 andvalue source factory 706. For each core record, default values for thedata in the core record may be provided by one or more default factoriesassociated specifically with that core record, while other parameters ineach core record, such as the provenance or lineage, may be provided forby the system. Default factory 704 includes entity record 704 a,computed expressions 704 b, and simple values 704 c. Entity record 704 amay be a reference to an entity record, which may have default valuesfor a new core record. For example, the name of the company would bestored in the entity referred to by entity record 704. Computedexpressions 704 b may involve information that may be programmaticallyderived. For example, given a number of shares and a fair market value,a default factory could compute the amount of cash required to exercisea stock option to purchase that number of shares. Simple values 704 care values that can be used directly as defaults for the given corerecord.

Similarly, in some embodiments, value source factory 706 includes entityrecord 706 a and manual text 706 b, but unlike the default factory,which provides default values for data in the core record, value sourcefactory 706 provides default sources for those values, i.e., defaultsfor provenance and/or lineage parameters. Entity record 706 a is similarto entity record 704 a in that value source factory entity record 706 ainstructs the system to assign to a given core record the default valuesource that is found in the entity record. Manual text 706 b is similarto simple value 704 c in that value source factory entity record 706 binstructs the system to indicate that the source of this value is manualtext entry; in some embodiments, manual text entry may be accompanied byinformation about the stakeholder that made the manual text entry. Insome embodiments, a core record can be a valid value source factory.

FIG. 8 is a schematic diagram of a workflow execution engine andcomponents relating thereto, in accordance with some embodiments.Workflow execution system 802 includes a workflow execution engine 802a, definition storage 802 b, and instance management 802 c. Systemstorage 824 includes entity 824 a, and associated with entity 824 a,documents 824 b, stakeholders 824 d, and process pointers 824 e, as wellas tags 824 c associated with documents 824 b. Workflow editor 820 iscoupled to definition storage 802 b and is operated upon by a lawyer822. Process 812 is in communication with instance management 802 c andalso with workflow data store 814, app data store 816, and state store818.

In operation, in some embodiments, workflow execution system 802 mayinclude an engine 802 a that performs processing of business logic,generates defaults, combines stored data from other records with datafor a current process, executes instructions in stored procedures anddocument templates, and sends information to a user interface (notshown) for display to the user. Workflow execution system 802 may alsoinclude definition storage 802 b, for storing one or more businessprocesses in XML Process Definition Language (XPDL) format and forcommunicating with workflow editor 820; and instance management 802 c,for managing one or more processes that are currently executing.Workflow execution engine 802 a may manage one or more queues for work,and may send work items 810 to a worker system (not shown) forprocessing. Work items 810 may be sent to the worker system with orwithout all the input required; the worker system may be responsible forcompleting work items, including searching for input as needed, in theorder queued or in another order if necessary for parallel processing.

In some embodiments, each workflow may require a process 812 to becreated that has workflow data 814, app data 816, and state 818.Workflow data 814 may store data available to the workflow engine, appdata 816 may store data relevant to application execution, and state 818may store data internal to process execution, where all of these datarelate to a specific business process received via workflow editor 820and definition storage 802 b. More than one process may be created,allowing for parallel processing over multiple business processes andentities.

In operation, lawyer 822 may use workflow editor 820 to administersystem 802. In some embodiments, the workflow editor 820 may be anintegrated development environment (IDE), either provided as desktopsoftware or web-based application software. The lawyer may be enabled toregister a new process definition (and in some embodiments, by uploadingan XML Process Definition Language (XPDL) file). The lawyer may also beenabled to register a new corporate action tied to an already-registeredprocess definition, in the process defining which roles have access tothe new corporate action. In some embodiments, lawyer 822 may also use atemplate building text editor (not shown) in conjunction with anadministrative web-based application to register a template with an ID,to upload a new document template, to extract and validate schemas fromthe uploaded document template, and to set entity and stakeholdermetadata references for the new template. An attorney or lawyer is notneeded to perform any of these steps and/or tasks, but “lawyer” is usedin a representative fashion to indicate what types of users maytypically be tasked with these operations.

FIG. 9 is a schematic diagram of a user interface in conjunction with aworkflow execution engine, in accordance with some embodiments. Workflowexecution system 802, including workflow execution engine 802 a,definition storage 802 b, and instance management 802 c are shown, asare system storage 824 with entity 924 a, and associated with entity 924a, documents 924 b, users 924 d, and process pointers 924 e, as well astags 924 c associated with documents 924 b. Process 812 is also shown,and is again in communication with instance management 802 c and alsowith workflow data store 814, app data store 816, and state store 818.Also depicted are user interface 902, operated upon by corporate officer904; wizard user interface (UI) 906; work item 810; and work item UI910.

In operation, user interface 902 may display active work items relevantto a user (i.e., corporate officer 904). The user may select a work itemfor execution (i.e., “document requires signature”), causing the workitem 810 and work item UI 910 to receive work. Work item 810interoperates with workflow execution system 802 and process 812 toperform necessary data management tasks. Work item UI 910 communicateswith wizard UI 906, if needed, and renders (or causes wizard UI 906 torender) any required visual indications of process context, completionstate, wizard flow, user-directed information requests, or any otheruser interface elements. Processing continues at work item 810 until theworkflow execution system 802 indicates that the process is complete.

FIG. 10 is a schematic diagram of a information structure, in accordancewith some embodiments. In some embodiments, an entity 1000 is ahigher-level object, and includes entity record schemas 1002 and entityrecord sets 1004, as well as document container 1006 and stakeholdercontainer 1008. In other embodiments, documents, processes, and/orstakeholders may exist as peers to the entity object, and may beassociated with but not contained within the entity object.

Entity record schemas 1002 may be a list of all possible data objects onthe system with a schema for each, and entity record sets 1004 may be alist of entity records specific to the entity 1000. Document container1006 may include all documents that are associated with entity 1000, andeach document instance 1006 a may include core record sets 1006 b,containing all core records for that document instance, and also aversion of the document in PDF format 1006 c. Document container 1006also includes all templates 1006 d, with each template being stored withboth a document template 1006 e and a core record schema 1006 f definingwhat data may be used for that document template.

Stakeholder container 1008 may include a set of stakeholder records 1008a, each including a stakeholder record set 1008 b that contains allstakeholder records associated with the specific stakeholder record.Additionally, stakeholder record schemas for stakeholders 1008 c may bepresent within stakeholder container 1008, in some embodiments.

FIG. 11 is a schematic diagram of a record schema, in accordance withsome embodiments. Record schemas 1102 includes a specific record schema1102 a, which includes a set of fields 1102 b, each having a type, whichmay include one of the following: text, textline, integer, currency,optional choice, signature, boolean, and date, or another type. Recordschema 1102 a does not contain any operational data pertaining to adocument, a stakeholder, or to a corporate entity.

FIG. 12 is a schematic diagram of a document templating architecture, inaccordance with some embodiments. Shoobx template (SBT) file 1202 cangenerate a metadata schema 1204 or an HTML snippet 1212. SBT file 1202is dependent on the document model described herein, and includesextensions to report markup language (RML) for handling terms andsections of documents. Metadata schemas 1204 define the input needed togenerate a given document. HTML snippets 1212 can be used to drive helptext, or to drive a paragraph-level preview of the document, or torender all or part of the document into HTML. In addition, SBT file 1202can be translated to an RML page template file 1206 containing businesslogic and/or executable instructions, which can be translated to astatic RML file 108, which can be used to generate a static PDF file1210. In some embodiments, an RML translation engine, such as ReportLab,may be used to translate RML to PDF. In some embodiments, the RMLtranslation engine may be used to translate RML to HTML.

FIG. 13 is a schematic diagram of components of a signature, inaccordance with some embodiments. Signature block 1300 may appearvisually on a document generated by the system. Signature preamble 1300a may contain basic language, such as the words “Signed,” or “Executedby,” or other language that may serve as a preamble. Signature image1300 c, QR code 1300 b, and signature unique ID 1300 d together compriseidentifying information initiated by a signing user, e.g., thelegally-binding signature. Signatory details 1300 e may be a text blockdescribing the identity of the signer and the authority held by thesigner, e.g., “John Smith, President.” Signatory details 1300 e may bederived automatically from the stakeholder's name and role.

In some embodiments, when a user elects to sign a document, a userconsents to apply his or her prior-assigned signature image 1300 c tothe document, and at that time a signature unique ID is generated. Sincethe signature unique ID is uniquely associated with the particularsignature assigned to this document, the exact document and page of thedocument may be retrieved by looking up the signature unique ID, evenwhen a large number of documents is present on the system. QR code 1300b is a visual representation of signature unique ID 1300 d, in someembodiments, for rapid search and retrieval of the signature databasebased on the signature unique ID. In some embodiments, not every elementin signature block 1300 may be used by the system as the standardsignature block.

FIG. 14 is a schematic diagram of document lookup via signature QRcodes, in accordance with some embodiments. At step 1408, a QR code of asignature is scanned at end user device 1402. At step 1410, the end userdevice 1402 decodes the signature UID from the QR code. At step 1412,the signature UID is sent to the business operating system 1406 itself.The document has not yet been identified and is bypassed. At step 1414,the system returns a document URL. At step 1416, the user's device maynow directly request document data from document 1404, and at step 1418,data is received at the end user device 1402 for the specific document1404.

FIG. 15 is a schematic diagram of users and stakeholders and theirsecurity roles, in accordance with some embodiments. Business operatingsystem 1500 includes an authentication module 1502 and an authorization1504. Authentication module 1502 is for identification of the user,e.g., is the user who he or she claims to be? Authentication module 1502includes credentials 1506 a and user records 1506 b for user 1506.Authorization module 1504 is for determining whether the specific usershould be permitted to take a specific action, e.g., has the user beenassigned the capability to perform this action? All records for theauthorization module relate to at least one specific entity 1504 a;additional entities are not shown but may be present. Stakeholder roles1508 a and stakeholder records 1508 b are associated with stakeholder1508. Additionally, stakeholder 1508 may have received delegated roles1510 a from stakeholder 1510. Authorization module 1504 also maydetermine what information the user has access to in the system.Authorization module 1504 may use roles to determine what information,actions, or capabilities the user has access to.

In operation, user 1506 may present his or her credentials to thesystem, which are matched against credentials 1506 a to verify theuser's identity at authentication module 1502. In some embodiments,two-factor or multi-factor authentication may be used. Once the user hasauthenticated, the user records 1506 b are retrieved by the system andall entities for which the user is a stakeholder are retrieved by thesystem as well, using the unique IDs for each user-stakeholder pair.Next, each user-stakeholder pair is evaluated for its roles 1508 a, 1510a to determine whether a certain task is permissible. As each roleincludes permissions for many different actions and access to variousinformation, role may be thought of as a keychain, containing many keys.In some embodiments, a context of the user on the system is taken intoaccount in addition to roles (e.g., additional capabilities may begranted to a human resources user when the actions are performed on orfrom a human resources landing page, sub-site, or section of the userinterface).

FIG. 16 is a schematic diagram of components involved in modifying andamending a document, in accordance with some embodiments. Document 310includes original portion 1602, which itself includes sections 1602 a,1602 b, 1602 c . . . 1602 n. Modifications are also stored with thedocument 1604, and in FIG. 16 modification has already been made tosection 2, 1604 a. A new amendment 1606 is being presented, with content1606 a, which includes amended section 3 content 1606 c. Approvals 1608and 1610 are needed to approve the amendment.

In operation, the original content 1602 of document 310 does not change,even when the document is subject to one or more amendments. This may bedisplayed in the user interface as an overlay or sidebar, indicatingthat the document has been modified but not presenting the modificationsas part of the original document. Modification of section 3 may begenerated by a process that generates amendments, which may be limitedto specific changes of core values stored in the document, or specificchanges such as complete cancellation; or which may include the abilityto amend any and all terms arbitrarily (e.g., rewrite the sectioncompletely). Approvals 1608 and 1610 may be initiated and requestedwithin the system. For example, if a document indicates that approvalsare needed, the system will identify the users to whom approvals shouldbe sent and will block the amending user from going forward until theapprovals have been received. Once approvals have been received, amendedsection 3 content 1606 c may be saved into document modifications 1604,and may be linked to section 3 in the way that section 2 modification1604 a is linked to section 2 of the original document.

FIG. 17 is a flowchart of a process that generates a document, inaccordance with some embodiments. At step 1702, a process starts, takinginto account a process, stored at process store 1702 a. Here, a genericcorporate agreement process is illustrated. At step 1704, the user isrequested to indicate whether or not a nonstandard document will beuploaded by the user. If the document is nonstandard, the user mayupload it at step 1705, but the user must input core records manually atstep 1707, which is a source of human error. The system may ask whetheror not the uploaded document needs to be signed or re-signed, at whichpoint the system either collects signatures at step 1714 or signs thedocument cryptographically at step 1716.

If no upload is selected at step 1704, the system may then applydocument template 1706 a, core record schema 1706 b, and entity records1706 c to compute core records for the new document. At step 1708,manual values for any additional core records that do not have defaultvalues are requested, based on the list of core records in the corerecord schema 1708 a. At step 1710, the core records may be combinedwith the document template stored at document template store 1710 a togenerate a human-readable document that the user may be invited toreview. At step 1712, following user review, the document may begenerated, again with reference as needed to document template 1712 a.At steps 1714 and 1716, the system will collect signatures and sign thedocument.

After the document has been cryptographically signed, the document canno longer be modified. The document may be stored, at step 1718, indocument store 1718 a. Typically a document will contain core recordsthat will change values stored in the entity record, so those changesare also saved at step 1720, in entity records store 1720 a. At step1722, execution stops.

FIG. 18 is a wireframe diagram of a terms selection page for aparticular section of a document, in accordance with some embodiments.Terms selection page 1800 includes header portion 1802, contextualnavigation control 1804, document navigation control 1806, processnavigation indicator 1808, detailed content area 1810, PDF display area1812, and process navigation control buttons 1814. As shown, a corporatemanager is in the middle of a business process for adding an employee,where the process includes both creation of an employment agreement anda confidentiality agreement; this macro view of the process is shown inprocess navigation indicator 1808. Certain controls relating to the roleof the logged-in user/stakeholder are shown in header portion 1802, andmay change based on the selection by the user of a specific role andentity. Contextual navigation control 1804 indicates certain informationrelating to the current process, either from prior data entry or fromthe system, that may be helpful for understanding the specific processbeing executed. Document navigation control 1806 provides a list ofheaders in a document. A user may make edits to document terms in themain section, detailed content area 1810, such as electing an industrystandard term, a starting date or a number of vacation days, among otherparameters; key data requests from the system may appear in this area.Navigation control buttons 1814 move forward or backward in atemplate-based or wizard-based process, or serve to return the user toanother screen where he or she can select tasks. In some embodiments,different visual indicators and controls may be provided, and thespecific user interface elements depicted in FIG. 18 need not all bepresent for every embodiment.

FIG. 19 is a schematic diagram of an example report card for anon-disclosure agreement, in accordance with some embodiments. Asdescribed above, a report card may provide a quick assessment of whethera document contains valid and actionable information about the corporateentity. Here, report card 1900 includes: a title 1902 that indicates thetype of document being described; a confidence indicator 1904 derivedfrom evaluation of a number of factors; an action audit list 1906showing the dates of all changes made by all users to the document; adocument term summary 1908 summarizing the document; and detailedinformation 1910 about core records in the document (“Key DataInformation”).

Detailed information 1910 may include sections pertaining to thedocument type itself 1910 a, here, to a non-disclosure agreement; to thecorporate entity 1910 b; to the document terms 1910 c; and to anyadditional core records in the document 1910 d, here, the counterparty(“discloser address”). The detailed information may include the valuestored in the document for each core record, and notably, the valuesource for each value, enabling a user or auditor to ensure that allvalues were derived properly and/or were not erroneously entered usingmanual data entry.

Alternatives

Having thus described several aspects of at least one embodiment of thisinvention, it is to be appreciated that various alterations,modifications, and improvements will readily occur to those skilled inthe art.

Such alterations, modifications, and improvements are intended to bepart of this disclosure, and are intended to be within the spirit andscope of the invention. Further, though advantages of the presentinvention are indicated, it should be appreciated that not everyembodiment of the invention will include every described advantage. Someembodiments may not implement any features described as advantageousherein and in some instances. Accordingly, the foregoing description anddrawings are by way of example only.

The above-described embodiments of the present invention can beimplemented in any of numerous ways. For example, the embodiments may beimplemented using hardware, software or a combination thereof. Whenimplemented in software, the software code can be executed on anysuitable processor or collection of processors, whether provided in asingle computer or distributed among multiple computers. Such processorsmay be implemented as integrated circuits, with one or more processorsin an integrated circuit component. Though, a processor may beimplemented using circuitry in any suitable format.

Further, it should be appreciated that a computer may be embodied in anyof a number of forms, such as a rack-mounted computer, a desktopcomputer, a laptop computer, or a tablet computer. Additionally, acomputer may be embedded in a device not generally regarded as acomputer but with suitable processing capabilities, including a PersonalDigital Assistant (PDA), a smartphone or any other suitable portable orfixed electronic device.

A computer may have one or more input and output devices. These devicescan be used, among other things, to present a user interface. Examplesof output devices that can be used to provide a user interface includeprinters or display screens for visual presentation of output andspeakers or other sound generating devices for audible presentation ofoutput. Examples of input devices that can be used for a user interfaceinclude keyboards, and pointing devices, such as mice, touch pads, anddigitizing tablets. As another example, a computer may receive inputinformation through speech recognition or in other audible format.

Such computers may be interconnected by one or more networks in anysuitable form, including as a local area network or a wide area network,such as an enterprise network or the Internet. Such networks may bebased on any suitable technology and may operate according to anysuitable protocol and may include wireless networks, wired networks orfiber optic networks.

The various methods or processes outlined herein may be coded assoftware that is executable on one or more processors that employ anyone of a variety of operating systems or platforms. Additionally, suchsoftware may be written using any of a number of suitable programminglanguages and/or programming or scripting tools, and also may becompiled as executable machine language code or intermediate code thatis executed on a framework or virtual machine.

In this respect, the invention may be embodied as a computer readablestorage medium (or multiple computer readable media) (e.g., a computermemory, one or more floppy discs, compact discs (CD), optical discs,digital video disks (DVD), magnetic tapes, flash memories, circuitconfigurations in Field Programmable Gate Arrays or other semiconductordevices, or any other tangible computer storage medium) encoded with oneor more programs that, when executed on one or more computers or otherprocessors, perform methods that implement the various embodiments ofthe invention discussed above. As is apparent from the foregoingexamples, a computer readable storage medium may retain information fora sufficient time to provide computer-executable instructions in anon-transitory form. Such a computer readable storage medium or mediacan be transportable, such that the program or programs stored thereoncan be loaded onto one or more different computers or other processorsto implement various aspects of the present invention as discussedabove. As used herein, the term “computer-readable storage medium”encompasses only a computer-readable medium that can be considered to bea manufacture (i.e., article of manufacture) or a machine. Alternativelyor additionally, the invention may be embodied as a computer readablemedium other than a computer-readable storage medium, such as apropagating signal.

The terms “program” or “software” are used herein in a generic sense torefer to any type of computer code or set of computer-executableinstructions that can be employed to program a computer or otherprocessor to implement various aspects of the present invention asdiscussed above. Additionally, it should be appreciated that accordingto one aspect of this embodiment, one or more computer programs thatwhen executed perform methods of the present invention need not resideon a single computer or processor, but may be distributed in a modularfashion amongst a number of different computers or processors toimplement various aspects of the present invention.

Computer-executable instructions may be in many forms, such as programmodules, executed by one or more computers or other devices. Generally,program modules include routines, programs, objects, components, datastructures, etc. that perform particular tasks or implement particularabstract data types. Typically the functionality of the program modulesmay be combined or distributed as desired in various embodiments.

Data structures may be stored in computer-readable media in any suitableform. For simplicity of illustration, data structures may be shown tohave fields that are related through location in the data structure.Such relationships may likewise be achieved by assigning storage for thefields with locations in a computer-readable medium that conveysrelationship between the fields. However, any suitable mechanism may beused to establish a relationship between information in fields of a datastructure, including through the use of pointers, tags or othermechanisms that establish relationship between data elements.

Various aspects of the present invention may be used alone, incombination, or in a variety of arrangements not specifically discussedin the embodiments described in the foregoing and is therefore notlimited in its application to the details and arrangement of componentsset forth in the foregoing description or illustrated in the drawings.For example, aspects described in one embodiment may be combined in anymanner with aspects described in other embodiments.

The invention may be embodied as a method, of which an example has beenprovided. The acts performed as part of the method may be ordered in anysuitable way. Accordingly, embodiments may be constructed in which actsare performed in an order different than illustrated, which may includeperforming some acts simultaneously, even though shown as sequentialacts in illustrative embodiments.

Use of ordinal terms such as “first,” “second,” “third,” etc., in theclaims to modify a claim element does not by itself connote anypriority, precedence, or order of one claim element over another or thetemporal order in which acts of a method are performed, but are usedmerely as labels to distinguish one claim element having a certain namefrom another element having a same name (but for use of the ordinalterm) to distinguish the claim elements.

The phraseology and terminology used herein is for the purpose ofdescription and should not be regarded as limiting. The use of“including,” “comprising,” or “having,” “containing,” “involving,” andvariations thereof herein, is meant to encompass the items listedthereafter and equivalents thereof as well as additional items.

The invention claimed is:
 1. A system for organizing, managing, andreporting data relating to a corporate entity, comprising: at least onedatabase configured to store a document record and a core record, thedocument record relating to a corporate action, the core record storedwith the document record; a business logic module, coupled to the atleast one database; and at least one document template stored in the atleast one database and comprising instructions for generating, at thebusiness logic module, a document based on the core record, the corerecord further comprising a value reflecting human-readable informationfor incorporation into the generated document, the core record furthercomprising a provenance of the value for allowing the business logicmodule to assess validity of the value at a given time by evaluatingwhere the value was originated, wherein the provenance of the valuereflects either manual entry or refers to another document based onanother core record, the value of the core record matching a value ofthe another core record, and the provenance reflecting a chain ofdocuments that together reflect a canonical state of the corporateentity and a history of states of the corporate entity, the businesslogic module thereby enabling the system to verifiably generatedocuments that reflect the canonical state of the corporate entity. 2.The system of claim 1, wherein the provenance is a source documentobject or an indication that the value was manually entered by astakeholder.
 3. The system of claim 1, further comprising a userinterface coupled to the business logic module for displaying thegenerated document to a user for signature.
 4. The system of claim 1,wherein the at least one database is configured to store an entityobject, the entity object further comprising a set of entity recordswith each entity record of the set of entity records comprising a valueand a provenance of the value, wherein at least one entity record of theset of entity records comprises a provenance that is the document objectrelating to the corporate action.
 5. The system of claim 1, furthercomprising a plurality of processors coupled to a database over anetwork.
 6. The system of claim 1, further comprising an authenticationmodule and an electronic signature manager configured to insertsignatures into generated documents.
 7. The system of claim 1, furthercomprising a retrieval module configured to accept a signature uniqueidentifier or quick response (QR) code related to a signature on apreviously-executed document for retrieving the stored document.
 8. Thesystem of claim 1, further comprising a delegation manager configured toperform authorization to perform an action in the system using one ormore of permissions, roles, principals or groups, and configured topermit principals to delegate a permission or role to another principalin the context of a particular entity, document, or process.
 9. Thesystem of claim 1, further comprising a user interface coupled to thebusiness logic module, wherein the user interface is configured todisplay available stakeholder capabilities, the stakeholder capabilitiesenabling a user to modify an entity record through a process.
 10. Thesystem of claim 1, wherein the generated document may be a portabledocument format (PDF) document.
 11. The system of claim 1, wherein thebusiness logic module is configured to retrieve, for a given entityrecord, a prior-generated document storing a core record referenced bythe given entity record and with an active status stored in a tag of theprior-generated document.
 12. A method for organizing, managing, andreporting data relating to a corporate entity, comprising: retrieving anentity record comprising a value and a lineage entry, the lineage entrycomprising a value source, the value source referencing a firstdocument; retrieving a corporate action stored as a computer-readableprocess definition; creating a core record for a second document basedon at least one of the entity record, a stakeholder record, or manualinput; and generating the second document using the core record and adocument template, wherein the value source of the value references thefirst document, the value of the core record matches a value of anothercore record of the first document, and the core record for the seconddocument reflects a chain of documents that together reflect a canonicalstate of the corporate entity and a history of states of the corporateentity.
 13. The method of claim 12, further comprising: retrieving apermissibility rule associated with a corporate action and an activestakeholder role; and determining, based on the permissibility rule andthe stakeholder role, whether a stakeholder is authorized to perform thecorporate action.
 14. The method of claim 12, further comprising:storing an active document status with the second document; andretrieving a set of documents that includes the second document inresponse to a query for all active documents, thereby enabling a user toretrieve documents that reflect a present state of the entity.
 15. Themethod of claim 12, further comprising: retrieving an updated value froma new core record within the second document; updating the entity recordwith the updated value; and adding, to the entity record, a new lineageentry with a value source referencing the second document, therebypreserving the first document without modification.
 16. The method ofclaim 12, wherein the first document is a certificate of incorporation,and the first core record is a corporation name referenced in thecertificate of incorporation.
 17. The method of claim 12, wherein thesecond document is one of a board resolution, a shareholder consent, ashareholder communication, and a stock plan.
 18. The method of claim 14,wherein the first document is a certificate of incorporation, and thesecond document is an amendment to the certificate of incorporation. 19.A system, comprising: a processor for performing data storage andretrieval operations; a database coupled to the processor; and a storagemedium comprising instructions which, when executed by the processor,performs steps comprising: retrieving an entity record comprising avalue and a lineage entry, the lineage entry comprising a value source,the value source referencing a first document; retrieving a corporateaction stored as a computer-readable process definition; creating a corerecord for a second document based on at least one of the entity record,a stakeholder record, or manual input; and generating the seconddocument using the core record and a document template, wherein thevalue source of the value references the first document, the value ofthe core record matches a value of another core record of the firstdocument, and the core record for the second document reflects a chainof documents that together reflect a canonical state of the corporateentity and a history of states of the corporate entity.